Understanding Ethereum txpool: Parameters, Queues, and Transaction Lifecycle

Txpool Startup Parameters

Geth provides several command‑line flags to control the behavior of the transaction pool. The most common options are: --txpool.nolocals – disables price exemption for locally submitted transactions. --txpool.journal "transactions.rlp" – path to the on‑disk log of local transactions (used for node restart). --txpool.rejournal 1 – interval in hours to rewrite the transaction log. --txpool.pricelimit 1 – minimum gas price required for a transaction to enter the pool. --txpool.pricebump 10 – percentage increase required over an existing transaction’s price to replace it. --txpool.accountslots 16 – minimum number of executable slots guaranteed per account. --txpool.globalslots 4096 – maximum number of executable slots across all accounts. --txpool.accountqueue 64 – maximum number of non‑executable (queued) transactions per account. --txpool.globalqueue 1024 – maximum total number of non‑executable slots. --txpool.lifetime 3 – maximum time (in hours) a non‑executable transaction can stay in the queue.

Viewing Txpool Content

You can inspect the current state of the pool with the RPC call: > txpool.content The result is a JSON object with two top‑level fields, pending and queued. Each field maps an address to a map of nonces and their corresponding transaction details.

Pending vs. Queued

Transactions with a nonce that matches the next expected nonce for the sender appear under pending. Transactions whose nonce is higher than the next expected value are placed under queued until the missing nonces are filled.

Example Scenario

Two transactions are sent from the same address:

> eth.sendTransaction({from: "0xdae19174969a7404e222c24b6726e4d089c12768", to: "0x5929a871f57a1C5F7E4eA304CAe92DACD1C1556b", value: web3.toWei(0.01, "ether"), gasPrice: 21000000000, nonce: 2});
"0x7db7883bb23a31deb9f01b5e6fb28363b1aee1b9b6797ea8b5706be170a1187c"

> eth.sendTransaction({from: "0xdae19174969a7404e222c24b6726e4d089c12768", to: "0x5929a871f57a1C5F7E4eA304CAe92DACD1C1556b", value: web3.toWei(0.01, "ether")});
"0x2784a79a8c454c72700e7be3b31c1c98ceaea232ca4992a6830b0fc999ebb653"

The first call explicitly sets nonce: 2, while the second omits the nonce. Because the address has never sent a transaction before, the omitted nonce defaults to 0. After executing txpool.content you will see the nonce 0 transaction under pending and the nonce 2 transaction under queued.

Txpool Processing Flow

If a transaction is submitted without a nonce, Geth calculates the highest nonce already used by that address, adds one, and places the transaction in pending. If a supplied nonce is larger than the next expected nonce, the transaction stays in queued until the missing nonces are filled. Sending a transaction with the missing nonce moves the previously queued transaction into pending:

> eth.sendTransaction({from: "0xdae19174969a7404e222c24b6726e4d089c12768", to: "0x5929a871f57a1C5F7E4eA304CAe92DACD1C1556b", value: web3.toWei(0.01, "ether")});
"0x7ee17d38405c01bab4eec4d9dc62a6bba98283e243a2d9132187706485878ef5"

> txpool.content
{ ... pending now contains both nonce 0 and nonce 1 entries, queued is empty ... }

Thus, filling the nonce gap automatically promotes the queued transaction to the pending pool.

Practical Tips

To avoid the pool being filled with low‑fee transactions, you can raise the minimum gas price either at runtime or via startup flags:

> miner.setGasPrice(51000000000)
true

Or start the node with: --gasprice "51000000000" The --txpool.accountqueue flag limits how many queued transactions each account can hold (default 64). Adjusting this value helps control memory usage on busy nodes.