A transaction you sent from MetaMask is sitting there with the word Pending next to it, and it’s been sitting there far too long. You can’t send anything else from the account, you can’t quite see what’s wrong, and every option in the wallet feels like a guess. It is one of the most stressful small experiences in crypto — but it is also one of the most fixable.
This guide explains, in plain language, why transactions get stuck, what the difference is between speeding a transaction up and cancelling it, how to cancel safely step by step, and what to do so it doesn’t happen again. By the end, a stuck transaction should feel like a minor plumbing problem rather than an emergency.
id=”why-transactions-get-stuck”>Why Transactions Get Stuck in MetaMask
Every Ethereum-style transaction you send has to win a spot in a block. Network participants who build blocks generally pick the transactions that pay the most gas — the fee attached to your transaction — because those earn them the most. If you set your gas price lower than what the network is currently demanding, your transaction waits. And waits. If you need a refresher on how these fees work, see our guide on what gas fees are.
There are a few common reasons a MetaMask transaction gets stuck:
- Gas price too low. The most common cause. You accepted a suggested fee (or typed your own) and the network got busier than expected right after.
- Nonce queue. Every transaction from your account has a number — a nonce — and they must be processed in order. If an earlier transaction is stuck, every transaction you send afterwards queues up behind it. That is why sending a new transaction doesn’t “fix” the old one; they line up.
- Network congestion spikes. Big events — token launches, NFT mints, market surges — flood the network and push the going gas price above what you set.
- Dropped from the mempool. Sometimes a transaction with very low gas simply falls out of the pool of unconfirmed transactions that nodes keep. It may eventually disappear rather than ever confirm.
Here is the reassuring part: a pending transaction is not lost money. Until a transaction is confirmed in a block, the funds technically have not moved. The wallet still shows your balance, but MetaMask marks the funds as committed while the transaction is pending. If the transaction is replaced or dropped, nothing was ever spent.
Speed Up vs Cancel: Which Should You Choose?
MetaMask generally offers two ways to deal with a stuck transaction: speed up and cancel. Both work on the same principle — sending a replacement transaction with the same nonce and a higher gas price — but they do opposite things.
| Speed up | Cancel | |
|---|---|---|
| What it does | Re-sends the same transaction with higher gas so it confirms faster | Sends a replacement transaction (usually to yourself) with higher gas that does nothing, replacing the stuck one |
| Same nonce? | Yes — the same nonce with a higher fee | Yes — the same nonce with a higher fee |
| Result | The original action still happens | The original action never happens; funds stay in your account |
| Cost | Higher gas fee than the original | Higher gas fee than the original (you pay gas even to cancel) |
| Use when… | You still want the transaction to go through — a swap, a bridge, an approval | You changed your mind, sent to the wrong place, or the original action is no longer needed |
| Risk | If you speed up with too little extra gas, it may stay stuck; you may then need to try again | If the original transaction confirms before the cancellation, you get the original result (rare but possible) |
A useful rule of thumb: cancel when you no longer want the transaction to happen; speed up when you still want it to happen, just faster. Either way, you are replacing the stuck transaction, not adding a second one — the network only ever accepts one transaction per nonce.
One thing beginners often miss: the replacement transaction must pay a meaningfully higher gas price than the stuck one — typically at least around 10% higher, and in practice often much more during congestion. A tiny bump may not be enough for the network to treat it as a genuine replacement.
How to Cancel a Pending Transaction Safely
The steps below describe the general process as of 2026. Wallet interfaces evolve, so menu names and button labels can differ slightly from what you see — but the logic is the same in any wallet that supports replacement transactions.
Step 1 — Check that it’s actually stuck. Give it a little time. A transaction that is only a few minutes old during a busy period may simply be working its way through. If it has been pending much longer than usual for that network and nothing is moving, it’s stuck.
Step 2 — Look at the current network fee. Before replacing anything, get a sense of what gas price transactions are confirming at right now. Gas trackers and block explorers publish live estimates. Your replacement needs to beat the current going rate, not just your original stuck fee.
Step 3 — Find the pending transaction in your activity list. In MetaMask, open the Activity tab. The stuck transaction should show as pending. Select it and look for the Cancel option (often near “Speed Up”).
Step 4 — Confirm the replacement transaction. MetaMask will propose a cancellation — typically a transaction sending 0 of the network’s native token to your own address, with the same nonce and a higher gas price. Check two things before confirming: that the destination is your own address, and that the gas price is high enough relative to current network conditions. You can often edit the gas to raise it.
Step 5 — Wait for the cancellation to confirm. The cancellation is itself a transaction, so it also needs to win a block slot. Once it confirms, the original transaction is dead — a transaction with the same nonce can never confirm afterwards. Your account is free and the queued transactions behind it should start flowing.
Step 6 — Verify. After the cancellation confirms, check your balance and activity. The original action should never have happened: no tokens moved, no swap executed. If something doesn’t look right, pause and investigate before sending anything new — don’t send a flurry of transactions while you’re confused.
Risks: Nonces, Double Spends, and Stuck Queues
Replacing transactions is safe when you understand the mechanics, but there are a few traps beginners fall into. Knowing them keeps a small annoyance from becoming a real problem.
Nonce confusion. The nonce ordering is the single most important concept here. If you have three stuck transactions (nonces 5, 6, 7), cancelling nonce 7 does nothing useful — nonce 5 is still blocking everything. Always deal with the lowest pending nonce first; the ones behind it will flow naturally once it’s cleared.
The original confirming anyway. When you cancel, there’s a brief race: if the original transaction somehow confirms before your cancellation reaches miners, the original wins and the cancellation becomes invalid. This is uncommon — the whole reason you’re cancelling is that the original fee was too low to confirm — but it’s why you should double-check the outcome rather than assume.
Custom nonce traps. Some guides tell you to cancel manually by sending a 0-value transaction to yourself with a custom nonce matching the stuck one. This works, but getting the nonce wrong is easy: too low and it fails; too high and you’ve created a new queue behind it. If your wallet offers a built-in cancel button, use it — it sets the nonce for you.
“Double spend” worries. Beginners sometimes fear that speeding up or cancelling could cause both transactions to execute. They can’t. The network enforces one transaction per nonce, full stop. What can happen is subtler: if you speed up a swap transaction, for instance, and prices moved while it was stuck, the swap may execute at a worse rate than you expected — check slippage and current prices before speeding up time-sensitive transactions.
Queued transactions burning fees. Remember that every replacement costs gas. If you cancel five queued transactions one by one, you pay five cancellation fees. It’s often cheaper and simpler to cancel just the oldest one and let the rest either confirm or be cancelled individually as needed.
How to Avoid Stuck Transactions in the Future
The best cancellation is the one you never need. A few habits make stuck transactions rare:
- Check gas before you send, not after. Glance at the current network fee level before confirming anything important. During busy periods, accept the higher suggested tier rather than picking the cheapest option.
- Don’t spam transactions. If a transaction is taking a while, resist the urge to send it again. Duplicates queue up behind the original and make the mess bigger.
- Use the wallet’s recommended gas for important transactions. The default suggestion is usually tuned to current conditions. Customising down to save a few cents is the most common cause of stuck transactions.
- Know where to watch. A block explorer lets you see whether your transaction is even visible to the network, what gas it carries, and how far behind it is. That information turns panic into a plan.
- Keep the network funded. You need the network’s native token to pay gas and to pay for cancellations. Trying to cancel a stuck transaction on a network where you hold zero native tokens is its own special frustration — keep a small reserve.
- Learn your wallet. Adding a new network is a good moment to get comfortable with wallet basics — see our guide to adding Polygon to MetaMask for a low-stakes walkthrough.
One more mindset shift worth making: stuck transactions are a normal part of using blockchains, not a sign you broke something. The network’s fee market is an auction, and low bids sometimes lose. Now you know how to bid again — or walk away — on your own terms.
FAQs
The Bottom Line
A pending MetaMask transaction is almost always just a gas-price problem, not a catastrophe. Speed up when you still want the transaction to happen; cancel when you don’t. Deal with the lowest stuck nonce first, make sure the replacement pays meaningfully more gas, and confirm the destination is your own address before approving a cancellation.
Keep a small gas reserve on every network you use, glance at network conditions before sending important transactions, and never let a stuck transaction push you into the arms of a “support agent” in your DMs. The plumbing is fixable — your seed phrase is not.
This guide is for education only — not financial advice.
