Nonce Too Low Error: What It Means and How to Clear It

29 October 2026

The "nonce too low" error means your wallet has submitted a transaction with a sequence number that the network has already processed or that is out of order. To clear it, you must either wait for the stuck transaction to confirm or replace it with a new transaction that has a higher nonce and a sufficient gas price.

What a Nonce Is and Why It Exists

Every Ethereum-compatible blockchain (including L2s like Arbitrum, Optimism, and Polygon) assigns a nonce to each transaction from a given address. The nonce is a counter that starts at zero. The first transaction you send from an address has nonce 0, the second has nonce 1, and so on.

The network requires that transactions be processed in strict nonce order. Node software will not include a transaction with nonce 5 in a block until the transaction with nonce 4 has been confirmed. This rule prevents replay attacks and ensures transactions are processed in the order the sender intended.

Why the error appears

The error occurs in two common situations:

You have a pending transaction with a lower nonce. If you send transaction A (nonce 4) and it remains unconfirmed while you try to send transaction B (nonce 5), the network will reject B because it cannot be processed before A. Most wallets and exchanges will show the error if they detect this mismatch.

You are using a wallet or dApp that has lost track of your nonce. Some wallets cache the nonce locally. If you send a transaction from another wallet or via a script, the local cache may become outdated. When your wallet then tries to send a transaction using a nonce the network has already used, the network rejects it.

You imported an account and the nonce counter reset. If you move a seed phrase to a new wallet, the new wallet may start counting nonces from whatever it sees as the next unused number. If it guesses wrong - for example, if a previous transaction was sent but never recorded locally - it will attempt a nonce the network has already consumed.

How to Clear the Error

The method depends on whether you have an unconfirmed transaction stuck with a lower nonce.

If you have a stuck pending transaction

1. Find the stuck transaction. Open your wallet's activity or transaction history. Look for a transaction that has been pending for longer than usual. Note its nonce and its current gas settings.

2. Speed it up (replace with same nonce, higher gas). Most wallets have a "speed up" or "replace" option. This sends a new transaction with the same nonce but a higher gas price. The network will prefer the new transaction because miners/validators prioritize higher tips. Once this new transaction confirms, the stuck one is invalidated and the error clears.

3. Cancel it (replace with a zero-value transaction to yourself). If speeding up is not working or you no longer want the transaction to go through, send a new transaction with the same nonce, a destination of your own address, a value of 0, and a gas price high enough to get confirmed quickly. This "cancel" transaction, once confirmed, replaces the original stuck transaction.

4. Wait. If the network is congested, the stuck transaction may eventually confirm on its own. Once it does, the nonce counter moves forward and you can send subsequent transactions normally.

If You Have No Stuck Transaction but the Wallet Is Confused

1. Reset your wallet's nonce cache. In MetaMask, go to Settings > Advanced > Clear activity tab data. This forces the wallet to re-fetch your account's nonce from the chain. Other wallets have similar options, often labeled "reset account" or "clear nonce."

2. Manually set the nonce. Advanced users can override the nonce in their wallet settings. Look for an "edit nonce" or "advanced gas controls" toggle. Set the nonce to the next unused number. You can find your current nonce by checking your address on a block explorer (e.g., Etherscan) under the "Transactions" tab - the nonce of your last confirmed transaction is the one to use; your next nonce is that number plus one.

3. Send a transaction with the correct nonce. Once the nonce is set properly, submit the transaction you originally intended. It will process normally.

What not to do

• Do not keep submitting the same transaction with the same nonce at the same gas price. The network will keep rejecting it, and you will waste fees on failed attempts.
• Do not create a new wallet and transfer funds out without fixing the nonce issue first. If you leave a stuck transaction, any subsequent transaction from that address that uses the same nonce will fail, potentially locking funds in the old wallet.
• Do not assume the error will fix itself if you wait indefinitely. A stuck transaction may never confirm if gas prices rise far above what you set. You must actively replace or cancel it.

When to Use a Block Explorer

If your wallet's built-in tools are not working, use a block explorer. Look up your address, find the stuck transaction, and note its nonce. Then use a wallet that allows manual nonce editing (such as MetaMask, MyEtherWallet, or Frame) to send a replacement transaction with that exact nonce and a higher gas price. This bypasses any wallet cache issues entirely.

A note on l2s

On L2s, the nonce system works the same as on Ethereum mainnet. However, some L2 sequencers have shorter transaction queues and may drop pending transactions after a timeout. If you see a nonce error on an L2, check whether the stuck transaction has been dropped entirely. If it has, your next nonce resets to the expected value, and you can simply send a new transaction. If not, the same replacement methods apply.

Back to gas fees