Locate a nonce gap in a Geth transaction pool
When later transactions from one sender remain queued, inspect the sequence visible to the node before changing prices or rebroadcasting anything.
Compare the account nonce with local pool entries
Read the sender’s transaction count at latest and use txpool_contentFrom for the same address on a Geth node exposing the txpool namespace. Suppose the chain expects nonce 41 and the pool contains only nonces 42 and 43.
chain next nonce = 41
local queue = 42, 43
A transaction at nonce 41 must be included before 42 can execute for that sender. Confirm the expected chain and look for the missing signed transaction in the originating application. Raising the fee on nonce 43 alone leaves the gap.
Separate local visibility from global inclusion
The pool is local to one backend, and admission or eviction can differ across peers. Check the chain state again before acting because a new block may already have consumed nonce 41. A hosted endpoint can disable these Geth-specific methods. geth.ethereum.org Geth txpool