MetaMask Transaction Stuck Pending Fixes
You open MetaMask, see a transfer sitting on Pending, and suddenly every new transaction is blocked behind it. If your MetaMask transaction stuck pending issue is happening right now, the good news is that it usually comes down to one of a few fixable causes: low gas, network congestion, a nonce conflict, or a wallet sync problem.
The fastest way to handle it is to figure out whether the transaction is actually waiting on the blockchain or just frozen inside the wallet UI. That difference matters, because the right fix for one can make the other worse.
Why a MetaMask transaction gets stuck pending
Most pending transactions are not true wallet failures. They are transactions that have been broadcast but are not attractive enough for validators to pick up yet. On Ethereum and other EVM networks, transactions with lower gas fees can sit for a long time when the network gets crowded.
There is also the nonce issue. Every transaction from your wallet uses a sequence number called a nonce. If one transaction with a lower nonce is stuck, the next one cannot move forward until that earlier one is confirmed, replaced, or canceled. That is why one bad transaction can jam everything behind it.
Sometimes the blockchain is fine and MetaMask is the part that looks wrong. A lagging wallet, a custom RPC problem, or a temporary sync issue can leave a transaction showing as pending even after the network already processed it.
First, check whether the transaction is really pending
Before trying to cancel anything, open the transaction details in MetaMask and view it on the block explorer for that network. Look for the transaction hash and see what the explorer says.
If the explorer shows Confirmed, your wallet display is out of sync. In that case, do not keep resending the same transfer. You are more likely dealing with a display or network connection problem inside MetaMask.
If the explorer shows Pending, the transaction is still waiting on-chain. Now the goal is either to speed it up or replace it.
If the explorer shows Dropped or Failed, the pending status in MetaMask may simply need a refresh or reset.
Fastest fixes for MetaMask transaction stuck pending
1. Use Speed Up in MetaMask
MetaMask often gives you a Speed Up option for pending transactions. This sends the same transaction again with a higher gas fee so validators are more likely to process it.
This is usually the safest first move. It keeps the same action and nonce but makes the fee more competitive. If the network is only mildly congested, this can clear the issue quickly.
Be realistic with the gas increase. A tiny bump may do nothing if traffic is heavy. If MetaMask offers low, market, and aggressive options, the aggressive setting is often the better choice when time matters.
2. Try Cancel if the transaction has not gone through
If you sent the wrong amount, used the wrong address, or simply want to stop the transfer, use Cancel in MetaMask if that button appears. This sends a new transaction with the same nonce and usually no value, designed to replace the stuck one.
This only works if the original transaction is still pending. If the original gets confirmed before the cancel request lands, the cancellation will fail. That is why timing matters.
Cancel also needs enough gas to beat the original pending transaction. If you choose too low a fee, the cancel request can get stuck too.
3. Reset account activity in MetaMask
If the block explorer shows the transaction is already confirmed, failed, or dropped, but MetaMask still shows it as pending, reset the wallet activity. In MetaMask settings, there is an option called Reset Account or Clear activity and nonce data, depending on app version.
This does not remove your funds or delete the wallet. It clears local transaction history and forces MetaMask to resync. For display issues, this is often the cleanest fix.
Still, make sure you are not resetting while a real pending transaction is active on-chain. If the explorer still shows Pending, deal with the transaction first.
When Speed Up and Cancel do not work
There are cases where MetaMask buttons fail, are missing, or keep spinning without fixing anything. Usually that points to a nonce problem or a network connection issue.
Send a zero-value transaction with the same nonce
This is the manual fix many advanced users rely on, but you can still do it carefully without being deeply technical. The idea is to send yourself 0 ETH or 0 tokens using the same nonce as the stuck transaction and a much higher gas fee. That replacement transaction pushes out the old one.
To do this in MetaMask, you may need to turn on custom nonce settings in Advanced settings. Then create a new transaction to your own wallet address, enter 0 for value if the network allows it, use the exact same nonce as the stuck transaction, and set a higher gas fee.
This works well, but only if you use the correct nonce. If you enter the wrong one, you can create more confusion instead of clearing it.
Switch networks or RPCs if the wallet is not syncing
If the explorer shows a different status from MetaMask, your RPC endpoint may be slow or unreliable. Switching to another approved RPC for that network, then reopening MetaMask, can refresh the wallet state.
This is especially common on smaller chains and custom network setups. The transaction may not actually be stuck. Your wallet may just be reading outdated data from a weak endpoint.
Update the MetaMask app or extension
An outdated wallet app can cause display bugs, failed gas estimates, or transaction actions that never submit properly. Check for an update in your browser extension store or mobile app store.
After updating, close and reopen the app, then check the transaction again on the explorer before taking another action.
Common reasons this keeps happening
Gas was set too low
This is still the main cause. If you manually lowered gas to save money, or accepted a low estimate during a traffic spike, the transaction may remain unattractive for a long time.
Low fees are not always a mistake. On quiet days they save money. But when speed matters, cheap gas often becomes expensive in another way because it delays everything else.
Network congestion is unusually high
NFT mints, token launches, bridge activity, and market volatility can flood networks with transactions. Even decent fees can get pushed aside during those spikes.
This is one of those it-depends situations. Sometimes waiting is enough. Other times the fee market moves fast enough that waiting just leaves your transaction buried.
Nonce conflicts from multiple transactions
If you submitted several transfers close together, especially across desktop and mobile, MetaMask can run into a nonce mismatch. One transaction gets stuck and everything after it queues behind it.
This is also more likely if you manually changed nonce settings before and forgot to switch them back.
Token approval or swap logic got stuck
Some pending items are not simple transfers. They are approvals, swaps, or smart contract calls. These can fail for more reasons, including slippage, contract conditions, or insufficient gas for execution.
In those cases, replacing the transaction may clear the queue, but the original action might still need to be re-entered with updated settings.
What not to do while a MetaMask transaction is stuck pending
Do not spam the same transfer over and over. That often creates more pending transactions or nonce conflicts.
Do not reset the wallet immediately without checking the block explorer first. If the transaction is genuinely pending on-chain, clearing local data will not solve the underlying issue.
Do not assume the funds are lost just because the wallet says Pending for a long time. Pending means unconfirmed, not necessarily failed.
Do not share your seed phrase with anyone claiming they can fix the issue. Real transaction troubleshooting never requires your recovery phrase.
A simple order to follow
If you want the least risky path, follow this order. Check the transaction on the block explorer. If it is still pending, try Speed Up first. If you need to stop it, use Cancel. If MetaMask and the explorer disagree, reset account activity. If buttons fail and the transaction remains pending, use a manual same-nonce replacement with a higher gas fee.
That sequence solves most cases without turning a temporary delay into a bigger mess.
If the transaction still will not clear
At that point, the issue is usually one of two things: the network is severely congested, or the wallet state is tangled by nonce conflicts across devices or apps. Waiting a bit can help in the first case. In the second, a manual replacement transaction is usually the cleaner fix.
If you are unsure whether to replace or wait, the block explorer is your best source of truth. MetaMask shows you what the wallet believes. The explorer shows what the network is actually doing.
A stuck crypto transaction feels worse than it usually is. Most of the time, you are dealing with fee math, queue order, or a sync problem, not a lost transfer. Stay methodical, verify the status first, and make one clear move at a time.
