Stuck Ethereum Transaction? How to Speed Up, Cancel, or Replace It in 2026

The Twelve-Hour Panic

You submitted a swap. An hour passes. The transaction is still pending. Your wallet shows three more queued behind it that cannot confirm either. You refresh Etherscan every thirty seconds hoping it moves.

I have been there. Everyone who uses Ethereum long enough has been there. The good news is that in 2026 this is a solved problem — the tools are mature, the fee mechanics are well-understood, and you can almost always get unstuck within minutes once you know where to push.

This guide walks through every scenario: why transactions get stuck, how to diagnose yours in under five minutes, how to speed up or cancel through MetaMask, when to drop to raw nonce replacement, and how to prevent the whole mess next time.

If you are new to gas mechanics entirely, read our explainer on what gas fees are and how they work first — this guide assumes you know the basics.

Why Transactions Get Stuck: The Three Real Causes

Cause 1: Max fee below current base fee

Under EIP-1559, every transaction specifies two values:

• maxFeePerGas: the absolute cap you will pay per unit of gas.
• maxPriorityFeePerGas: the tip paid directly to the validator on top of base fee.

The network's base fee floats from block to block, rising when blocks are full and falling when they are empty. If the base fee rises above your maxFeePerGas after you submitted, the transaction becomes ineligible for inclusion and just sits in the mempool.

This is the single most common stuck-transaction cause in 2026. During NFT mints, airdrop claims, or sudden market moves, base fee can spike from 5 gwei to 100 gwei in minutes. Any wallet that guessed 20 gwei as its max is stranded.

Cause 2: Priority fee too low to be attractive

Even with maxFeePerGas high enough, validators still pick the transactions with the highest effective priority fee first. If every recent block included transactions at 2 gwei tip and you set 0.5 gwei, builders simply skip yours.

Cause 3: Nonce blocked by an earlier stuck transaction

Nonces are strict. If your account has stuck nonce 42, then nonce 43, 44, and 45 cannot mine regardless of their fees. You have to fix 42 before anything else moves.

This cascade is especially bad on trading accounts that submit many transactions per hour: a single laggy approval can stall a whole position.

Step 1: Confirm the Transaction Is Actually Stuck

Open Etherscan and paste your transaction hash. The statuses you will see:

• Pending: still in the mempool, can be replaced.
• Success: already mined. Nothing to do.
• Failed: mined but reverted. Not stuck; the transaction executed but hit an error in the contract.
• Dropped: removed from the mempool due to time or resource pressure. The nonce is free; you can submit a new transaction at the same nonce.

If it is pending and has been for more than ~15 minutes under normal network conditions (or ~1 hour during congestion), it is stuck. Proceed to Step 2.

If your wallet shows pending but Etherscan cannot find the hash at all, your node never propagated it. Check your wallet is connected to the right RPC — this happens to people running their own nodes more than they realize.

Step 2: Compare Your Fees to Current Mempool Conditions

Open the Etherscan gas tracker or ultrasound.money. Note:

• Current base fee
• Suggested priority fee (usually 1-3 gwei in normal conditions)
• Recent confirmed transaction tips

Now compare to your stuck transaction. On Etherscan, the transaction detail page shows Max Fee, Max Priority Fee, and Base Fee Per Gas in the advanced details.

If maxFeePerGas < current base fee: the transaction cannot mine until base fee drops. Replace with a higher cap.

If maxFeePerGas >= current base fee but maxPriorityFeePerGas is very low: validators are deprioritizing you. Replace with a higher tip.

If both numbers look fine: check for a lower-nonce stuck transaction on the same account (see Cause 3).

Step 3: The MetaMask Fast Path

For 95 percent of stuck transactions, MetaMask's built-in UI is all you need.

1. Open MetaMask and select the correct account and network.
2. Click the Activity tab.
3. Click the pending transaction.
4. You will see Speed Up and Cancel buttons at the top.

Speed Up opens a fee editor pre-filled with a 10 percent bump (the geth minimum for mempool replacement). You can choose Market, Aggressive, or Custom. Custom lets you set maxFeePerGas and maxPriorityFeePerGas directly.

Cancel does the same thing but submits a 0 ETH self-transfer at the same nonce. If the cancel replacement wins the race, the original is effectively voided. If the original mines first, the cancel fails and you have paid a small amount of gas.

How much to bump

The mempool replacement rule requires both gas fee fields to be at least 10 percent higher than the original. This is a floor, not a recipe.

In practice:

• Gentle bump (+15-25%): use when network is calm and you just want a nudge.
• Aggressive bump (+50-100%): use during congestion; guarantees inclusion in the next few blocks.
• Nuclear bump (2-5x): use when you absolutely need it in the next block (airdrop claim, liquidation).

Every bump is a new max fee — if it still does not mine, you can bump again from there.

Step 4: Manual Nonce Replacement for Power Users

MetaMask's UI handles the common case. For edge cases — custom nonces, wallet disagreement about nonce, batched transactions — you need to do it manually.

Find the nonce

On Etherscan, click the transaction and look at the Nonce field in the advanced details. Or in MetaMask, the transaction detail shows the nonce in the bottom section.

Build a replacement in MetaMask

1. Settings > Advanced > Customize transaction nonce > ON.
2. Start a new transaction (any send, swap, or contract interaction).
3. At the confirmation screen, edit the nonce to match the stuck transaction's nonce.
4. Set fees well above current base fee and tip.
5. Confirm.

Ethereum will process whichever transaction mines first at that nonce; the other becomes invalid and drops out of the mempool.

Build a replacement with ethers.js

For scripted or high-frequency operations:

import { ethers } from "ethers";

const provider = new ethers.JsonRpcProvider(process.env.RPC_URL);
const wallet = new ethers.Wallet(process.env.PRIVATE_KEY, provider);

const stuckNonce = 42; // whichever nonce is stuck

// Cancel: 0 ETH self-transfer at the same nonce
const tx = await wallet.sendTransaction({
  to: wallet.address,
  value: 0n,
  nonce: stuckNonce,
  maxFeePerGas: ethers.parseUnits("150", "gwei"),
  maxPriorityFeePerGas: ethers.parseUnits("5", "gwei"),
});

console.log("Cancel submitted:", tx.hash);
await tx.wait();
console.log("Cancel confirmed");

The same pattern speeds up a transaction — just rebuild the original transaction (to, value, data) at the same nonce with higher fees.

Step 5: When to Use Flashbots Instead

Public mempool replacement races are themselves subject to MEV. If your transaction is large or profitable to front-run (big swap, NFT mint, arbitrage), searchers will detect your speed-up and sandwich it.

Flashbots Protect gives you a private RPC endpoint. Transactions submitted there go directly to block builders, bypassing the public mempool entirely. To use it:

1. Add the Flashbots Protect RPC as a custom network in MetaMask (or point your wallet there).
2. Submit the speed-up or replacement through that RPC.
3. The transaction becomes visible on-chain only when mined.

This is also the right tool if you suspect your public transaction has been picked up by a sandwicher who will crowd out any replacement you attempt.

For background on Ethereum's transaction model, see our explainer on what Ethereum is.

Step 6: Account Abstraction Sidesteps Most of This

ERC-4337 account abstraction wallets do not have the same nonce cascade problem. UserOperations use a flexible nonce space with "keys" and "sequences", so you can have multiple parallel nonce streams from the same account. A stuck operation in one key does not block another key.

Smart wallets like Safe, Argent, and Coinbase Smart Wallet also offer built-in replacement and cancellation UIs that handle fee bumping for you. If you find yourself regularly stuck, migrating off a standard EOA is the right long-term answer.

Real Scenarios I Have Debugged

Scenario A: NFT mint disaster

User set maxFeePerGas to 30 gwei for an anticipated mint. At mint time, base fee spiked to 400 gwei from coordinated mint activity. Transaction stranded for 6 hours, along with 4 queued approvals behind it.

Fix: cancelled the mint with a replacement at 500 gwei max, 10 gwei priority. Cancel confirmed within 2 blocks. The 4 queued approvals then processed in order normally.

Scenario B: Wallet says confirmed, Etherscan says pending

User's wallet showed the transaction as mined. Etherscan showed pending. Wallet was connected to a cached RPC that had forked briefly. Cleared wallet cache, reconnected to a fresh RPC (Alchemy or Infura), and the real status surfaced.

Scenario C: Nonce disagreement

User submitted transactions from two devices simultaneously. Both used nonce 17. One confirmed; the other stayed pending forever because nonce 17 was already used. The "stuck" transaction was actually invalid.

Fix: submit a new transaction at nonce 18 to resync the wallet's nonce counter. The old pending will eventually drop.

Scenario D: Revoke.cash revoke stuck

User revoking a token approval after seeing their wallet on revoke.cash. Revoke transaction stuck at low gas. Meanwhile a scam contract had already been called — the revoke needed to win the race.

Fix: re-submitted the revoke via Flashbots Protect at 3x normal fees. Landed in the next block. This is a case where gas price truly matters in real time.

Prevention Playbook

1. Set realistic defaults. Configure MetaMask Advanced > Default gas limit and fee settings. Do not leave it on "low" for anything time-sensitive.
2. Watch base fee before submitting. Thirty seconds on Etherscan gas tracker saves hours of waiting.
3. Avoid back-to-back submissions. If you submit 5 transactions in rapid succession, each at the same fee, and base fee rises between them, you will strand the last ones. Space them out or bump later ones proactively.
4. Use L2s for casual activity. Arbitrum, Optimism, and Base gas is so low that stuck transactions are effectively impossible. Save mainnet for operations that require it.
5. Switch to a smart wallet for trading. Account abstraction eliminates nonce cascades entirely.

When Nothing Works, Just Wait

Stuck transactions eventually drop out of the mempool — typically 3 hours on well-run nodes, up to 24 hours across the broader network. If the transaction is not time-sensitive and the fee is only slightly low, waiting is free and risk-free. You have not spent any gas until the transaction mines.

Once dropped, your nonce is free again and you can submit normally. Verify via an Etherscan check that the pending status has gone to dropped before assuming the nonce is clear.

What to Read Next

• What Are Gas Fees? Ethereum Fees Explained
• What is Ethereum? A Beginner's Guide
• ERC-4337 Account Abstraction Developer Guide

External references:

• Etherscan Gas Tracker
• EIP-1559 Specification
• Flashbots Protect RPC
• MetaMask Support: Speed Up / Cancel
• Ultra Sound Money (Base Fee dashboard)

This post is part of our Ethereum and DeFi coverage. For the broader picture, see our [complete guide to Ethereum](/blog/what-is-ethereum-explained).