MetaMask queued transaction blocking new transactions fix
MetaMask manages outgoing transactions with a sequential numbering system called nonces. Each address has a nonce counter that starts at zero. Every transaction you send increments that counter by one. The network enforces this ordering. Transaction 5 cannot be mined until transaction 4 has been confirmed or replaced.
This creates a problem. If one transaction gets stuck in the queue - waiting too long, underpriced, or simply unprocessed by the network - every transaction you attempt afterward will also stall. MetaMask will show them as queued, pending, or simply never broadcast them to the mempool.
The user sees a frozen wallet. Nothing new goes through. The root cause is always the same: a single transaction with a lower nonce that has not yet been included in a block.
Speed up or cancel the queued transaction
MetaMask provides two buttons on each pending transaction: Speed Up and Cancel. Both work by sending a replacement transaction with the same nonce as the stuck one.
Speed Up broadcasts a new transaction with a higher gas price. The network will prioritize the one offering more fees to miners. If the original transaction has not yet been included, the higher-gas version replaces it. This is the simplest fix for a transaction that simply needs faster confirmation.
Cancel broadcasts a zero-value transaction to your own address, again using the same nonce but with a higher gas price. The effect is the same: the original transaction is replaced. No funds move, and the nonce increments so the queue can proceed.
Both methods depend on the original transaction still being replaceable. Once a transaction has been picked up and included in a block, neither speed up nor cancel will work.
Send a custom-nonce transaction to bypass the queue
MetaMask allows advanced users to set a custom nonce directly. This is not enabled by default. You need to go into Settings, then Advanced, and toggle "Customize transaction nonce."
Once enabled, you can create a new transaction and manually assign it a nonce that is higher than the stuck one. The network will accept it, but it will also remain unconfirmed until the lower nonce is filled. This does not fix the blockage. It only lets you queue additional transactions in advance.
Use this method only if you expect the stuck transaction to clear soon. Otherwise you end up with multiple pending transactions at different nonces, and the same stall applies to each.
Account reset to clear local transaction history
MetaMask stores a local list of every transaction you have broadcast. If the network has already processed a transaction but MetaMask has not updated its local state - due to a bug, a cache issue, or switching networks - the wallet may still treat the transaction as pending.
This is more common than many users expect. The local queue disagrees with the actual state of the blockchain.
You can reset the account. In MetaMask, go to Settings, then Advanced, and click "Clear activity tab data." This wipes the local transaction history. MetaMask will then re-sync from the blockchain. Any transaction that was actually confirmed will disappear from the pending list. Any transaction that was never broadcast will also disappear.
This does not affect your balances or send any new transactions. It only fixes a discrepancy between what MetaMask believes and what the chain knows.
Important: resetting the account will also remove any locally stored pending transactions that you intended to broadcast but never did. Make sure you have the details of any important transaction before performing a reset.
What does not work
Waiting indefinitely often fails. The network does not automatically drop low-fee transactions. Some miners include them eventually, but there is no guarantee. The same applies to restarting MetaMask or switching RPC endpoints - those actions refresh the connection but do not alter the nonce or the stuck transaction.
The only reliable fixes are the three described above. Each addresses a different cause. Speed up or cancel handles a transaction that is still pending on the network. Custom nonce allows you to plan ahead but does not clear the blockage. Account reset fixes a local display error where the transaction is already confirmed but still shows as pending.
Prevention
Set gas fees realistically. Network congestion varies. Using the suggested fee from MetaMask or a gas oracle reduces the chance of a stuck transaction. Avoid sending multiple transactions in rapid succession unless you are certain the first one will confirm. Monitor the nonce counter.
One stuck transaction can halt an entire session. The fix is straightforward once you understand the nonce ordering. The blockchain will not process transaction 5 before transaction 4. That is not a bug. It is the design.
Not financial advice. lingose.games publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.