One stuck transaction, everything stuck
Send an Ethereum transaction with too low a fee and it can sit pending for hours. Transactions sent after it, even with generous fees, stall too. Transactions from an Ethereum account are processed strictly in order of a counter called the nonce.
This guide explains, with a hypothetical pending queue, how the nonce sets transaction order and why one stuck transaction holds up the rest. It covers replacing or cancelling a transaction with the same nonce and a higher fee, the limits of doing so, and what to check.
What the nonce does
Ethereum.org's page on transactions explains that the account nonce is a counter of transactions sent from that account and is used to prevent replay attacks, where the same transaction is processed twice. An account's first transaction has nonce 0, the next 1, and so on, and the network processes only the transaction carrying the next nonce in sequence.
If the transaction with nonce 42 is not processed, transactions with nonces 43 and 44 cannot enter a block however high their fees. Wallets typically determine the next nonce with requests such as eth_getTransactionCount, described in Ethereum.org's JSON-RPC documentation.
A hypothetical pending queue
The table shows a hypothetical account with transactions processed through nonce 41 and three transactions pending. The nonce 42 transaction's maximum fee is below the current base fee, so it cannot be included.
| Nonce | Transaction | Max fee (gwei) | Status | Response |
|---|---|---|---|---|
| 41 | Token approval | — | Processed | — |
| 42 | Send 0.5 ETH | 20 (current base fee 35) | Pending, fee too low | Replace with the same nonce and a higher fee |
| 43 | Swap | 60 | Waiting for 42 | Proceeds once 42 is processed |
| 44 | NFT purchase | 60 | Waiting for 42 and 43 | Cancel with the same nonce if no longer wanted |
Nonces 43 and 44 cannot enter a block until 42 is processed, even though their fees are sufficient.
Replacing and cancelling
A pending transaction can be replaced by sending a new one with the same nonce and a higher fee. Many nodes accept a replacement only if its fees exceed the original's by a minimum percentage, so wallets' speed-up features usually raise both the maximum fee and the priority fee. In the example, resending nonce 42 with a maximum fee of 45 gwei makes inclusion much more likely.
Cancelling means sending a transaction of 0 ETH to yourself with the same nonce and a higher fee. A transaction that does nothing takes the nonce instead of the transfer. It still costs a fee: 21,000 gas for a simple transfer at 45 gwei is about 0.000945 ETH.
When replacement fails
If the original transaction is included before the replacement or cancellation, the original executes as sent, because only the first included transaction with a given nonce counts. A cancel request works only while the original is still unprocessed.
The RPC node your wallet uses may see a different set of pending transactions from other nodes. A wallet may show a transaction as pending when it never propagated, or keep showing it after it was already processed. Checking the account's current nonce in a block explorer is more reliable.
Some wallets also keep a local record of pending transactions that survives after the network has dropped them. Clearing that local queue, or resetting the account's activity in the wallet settings, can be necessary before new transactions pick the right nonce.
Checks for a stuck transaction
If a transaction has been pending for a long time, work through these steps.
- In a block explorer, find the account's last processed nonce and any pending nonces.
- Check whether the lowest pending nonce's maximum fee is below the current base fee.
- If you still want it, replace it with the same nonce and a higher fee; if not, cancel by sending 0 ETH to yourself.
- Reconsider whether later transactions are still fine to execute once the earlier one clears.
- If you set nonces manually, take care not to reuse one that is already taken.
Later transactions can change meaning
If the front transaction is processed hours late, the swaps or purchases waiting behind it execute that much later too. If prices move meanwhile, a swap may revert on its minimum output and still cost a fee, and an NFT purchase may fail because someone else bought it.
As Ethereum.org's page on gas explains, fees change constantly with demand for block space. When sending several important transactions in a row, wait for the first to be processed before sending the next, or set generous fees from the start.
Limits of the explanation
The fees and nonces here are hypothetical. The minimum increase required for replacement depends on client and node settings, and wallets implement speed-up and cancel differently.
When dealing with a stuck transaction, check Ethereum.org and your wallet's current guidance, checking how recent each one is. Any decision remains yours, based on your own circumstances and risk tolerance.