Fixing queued transactions with the account nonce not in sequence

Fill the gap between the last transaction with the account nonce in sequence and the transaction with the account nonce not in sequence

This article applies to:

• Ethereum
• Polygon
• BNB Smart Chain
• Avalanche
• Fantom
• Harmony

Issue

You have a transaction not propagating to the node because the transaction's account nonce is not in sequence.

Example

Transaction from account 0x123... with account nonce 0 is propagated.

Transaction from account 0x123... with account nonce 12 is in the queued state and not propagated.

Cause

Transactions from an account are propagated to the network with the account nonce in sequence.

Example

Transaction from account 0x123... with account nonce 0 is propagated.

Transaction from account 0x123... with account nonce 1 is propagated.

Transaction from account 0x123... with account nonce 3 is not propagated until a transaction with the account 2 is created.

Solution

Fill the sequence gap by creating the transactions with the account nonce in sequence until the account nonce of a queued transaction is reached.

See also:

• Difference between pending and queued transactions on an EVM node
• Checking pending and queued transactions in your EVM node's local pool