Skip to main content
Aeterna Sol

Crypto markets, protocols and policy

Ethereum transaction nonces and sequential ordering

A nonce in an Ethereum transaction is its account’s sequence number: it orders transactions, prevents repeats and explains why a pending bridge approval can hold up a deposit.

The Aeterna Sol Editors

Ethereum transaction nonces and sequential ordering

An Ethereum transaction nonce is the account’s sequence number: it starts at 0 and rises by 1 each time that account sends a transaction.

Think of it like a numbered ticket in a queue. Your wallet assigns each outgoing transaction the next number for your account on that chain. Ethereum uses the number to order transactions and prevent the same transaction from executing twice.

What does an Ethereum nonce count?

A nonce counts transactions sent from one externally owned account, such as the account you control in MetaMask. “Externally owned” means the account is controlled by a private key. Its first transaction has nonce 0, the next has nonce 1, and the counter increases by one each time it sends a transaction.

The nonce is not a transaction fee or a measure of how much ETH you send. It marks the transaction’s place in that account’s sequence. The Ethereum Yellow Paper defines the account nonce as a counter for the number of transactions sent from the account; Ethereum.org’s Transactions documentation explains how the sequence keeps transactions in order.

Each nonce can be used for only one included transaction. If your account has a transaction with nonce 7 waiting, a transaction with nonce 8 cannot be included first. It must wait until nonce 7 is included, so the sequence stays in order.

Why can a pending bridge transaction hold up the next one?

A pending transaction with a lower nonce blocks later transactions from the same account on the same chain. Say you send a token approval on Ethereum with nonce 7 and set a low fee. The approval stays pending because it has not been included in a block.

You then sign a bridge deposit from the same Ethereum account. It gets nonce 8, but it cannot be mined before nonce 7. The Polygon bridge is the service used to move supported assets between Ethereum and Polygon PoS; that context helps explain why an approval and a deposit can be separate Ethereum transactions in the same queue.

Your wallet may show the deposit as pending too, even if its fee is higher. The later transaction cannot pass the earlier nonce. Until nonce 7 is included or replaced, nonce 8 and any still later transactions from that account on Ethereum remain queued behind it.

This is why a stuck approval can delay a deposit even though the approval and deposit have different purposes. The nonce tracks the sending account’s order, not what each transaction is meant to do.

How can you replace a stuck transaction?

You can unblock the queue by sending a replacement transaction with the same nonce and a higher fee. For the pending approval at nonce 7, you can use your wallet’s speed-up option to resubmit it with a higher fee. If the replacement is included, nonce 7 is resolved and the deposit at nonce 8 can proceed.

If you no longer want the original transaction, you can try to cancel it by sending a 0-ETH transfer to your own address with the same nonce and a higher fee. This self-transfer competes with the pending transaction for nonce 7. Only one transaction using that nonce can be included, so if the cancellation is included, it takes the place of the original and clears the way for nonce 8.

In either case, the replacement needs the same nonce as the pending transaction. Sending another transaction with a new, higher nonce would join the queue behind it, rather than clear the earlier item. A replacement also has to be accepted and included before the waiting transaction can move forward.

Does the same address have one nonce on every chain?

No. Ethereum and Polygon PoS keep separate nonce counts, even when you use the same address in MetaMask. Each chain orders transactions sent from that address on its own.

So if nonce 7 is stuck on Ethereum, it blocks later transactions from your account on Ethereum. It does not block a transaction you send from the same address on Polygon PoS. The two chains have separate transaction queues, and each uses its own next nonce.