How to Fix Replacement Transaction Underpriced in MetaMask (2026)

Replacement transaction underpriced in MetaMask usually means you tried to replace, speed up, or cancel a pending transaction using the same nonce, but the new fee settings were not high enough for the network to accept the replacement. It is not the same problem as insufficient funds, out of gas, or a broken contract path. It is mainly a pending-transaction repricing problem.

Intent check: This page is for the specific replacement-transaction-underpriced error. If you need the broader replace-or-cancel workflow first, read How to Speed Up or Cancel a Pending Transaction in MetaMask. If you first need the cause analysis, read Why Is My Crypto Transaction Pending?

This query usually appears in a high-stress moment. The wallet may feel stuck, the user may have clicked speed up twice, or a custom transaction may be competing with an older one. That is why the safest guide is not just a definition. It needs to explain what the error means, why it happens, and how to recover without making the queue messier.

What Replacement Transaction Underpriced Actually Means

On EVM networks, each wallet address sends transactions in sequence using a nonce. When a transaction is already pending, any new transaction with that same nonce is treated as a replacement attempt. Nodes and validators will usually ignore the replacement unless it offers a clearly better fee package than the old one.

That is why the message includes the word underpriced. The wallet is not saying the network fee is cheap in general. It is saying the replacement is not attractive enough compared with the version already sitting in the mempool.

Why MetaMask Shows the Error

MetaMask often surfaces this error in four situations:

• You tried to speed up a pending transaction but the new max fee or priority fee was only slightly higher.
• You tried to cancel a pending transaction but the cancel transaction was not priced aggressively enough to win the same nonce slot.
• You used custom nonce settings and accidentally created a second transaction that conflicts with the first one.
• Your wallet view is stale and you are acting on an older pending state while the network has already moved on.

During congestion, the threshold for replacing a pending transaction can rise quickly. A tiny fee bump that might have worked in calm conditions can fail when the mempool is crowded and validators have better-paying options available.

Common Situations Behind the Error

1. A stuck transaction is still pending

This is the classic case. You submitted a swap or transfer, it did not confirm, and then you attempted to resend or cancel it. If the fee increase is too small, the replacement does not take hold.

2. You clicked speed up more than once

When users panic, they sometimes create overlapping retries. That can produce a messy queue of pending intents, especially if the wallet or RPC lags behind the chain state.

3. You sent a new transaction before the old one cleared

Because nonces are sequential, one stuck transaction can block later ones. Sending more transactions without clearing the pending item first can keep compounding the problem.

4. You used manual gas settings without checking the network

Custom settings are useful, but only when you understand how they compete in the live fee market. If the replacement looks only marginally better than the old transaction, nodes may still reject it.

How to Fix Replacement Transaction Underpriced Safely

1. Check whether the original transaction is still pending on chain. Use the transaction hash, your wallet activity, or a block explorer. If the original transaction already confirmed, you are no longer solving a replacement problem.
2. If the original transaction is pending, use one clean replacement path. Either speed it up or cancel it from the same wallet, not both repeatedly at random.
3. Increase the replacement fee meaningfully. In practice, the new max fee and priority fee usually need to be clearly higher than the old values, not just a minimal nudge.
4. Avoid sending several competing replacements. One deliberate replacement is safer than a burst of retries that are all slightly different.
5. If MetaMask looks desynced, confirm the chain state before resetting activity. Resetting too early can hide what is actually still pending on chain.

A Safer Recovery Workflow

If you want a clean troubleshooting sequence, use this order:

1. Open the pending transaction and record the hash and nonce.
2. Check whether the network still shows it as pending.
3. If yes, decide whether you want to confirm it faster or replace it with a cancel.
4. Submit one replacement with clearly stronger fees.
5. Wait for the chain response before trying anything else.

This is also why the companion guide on speeding up or canceling a pending transaction in MetaMask is often the next step after this error appears.

Mistakes That Make the Problem Worse

• Confusing it with insufficient funds: if the wallet lacks the native gas token, that is a different error and a different fix.
• Confusing it with out of gas: out of gas is about execution allowance, not nonce replacement.
• Blindly copying fee values from an old pending transaction: the network may require a stronger bump now.
• Spamming retries: this can create more confusion than clarity, especially when the UI lags behind the mempool.
• Resetting activity before confirming the explorer state: that can hide a still-pending transaction and lead to duplicate actions.

Replacement Transaction Underpriced vs Other MetaMask Gas Errors

• Insufficient funds for gas: you do not have enough native token to pay the fee. Read this guide.
• Out of gas: the transaction did not have enough gas units allocated to finish. Read this guide.
• Gas settings confusion: you are trying to understand max fee, priority fee, or gas limit fields. Read this guide.

FAQ

Does replacement transaction underpriced mean my wallet is broken?

No. It usually means the network rejected the new replacement because it was not priced high enough relative to the pending one.

Can I just wait instead of replacing the transaction?

Sometimes yes. If the original transaction is still valid and the network calms down, it may eventually confirm. The decision depends on urgency and whether you still want that exact action to execute.

Why does this happen more during busy market conditions?

Because pending transactions compete harder during congestion. When block space becomes expensive, nodes are less willing to accept weak replacements.

Final Take

Replacement transaction underpriced is best understood as a nonce replacement pricing problem, not a generic MetaMask gas failure. If you confirm the original pending state, choose one clean replacement path, and bump the fee deliberately, the error becomes much easier to solve without creating a longer queue.

Related: Speed Up or Cancel a Pending Transaction in MetaMask | Understanding Nonce Errors in Crypto | What Is a Mempool in Crypto | What Is Network Congestion in Crypto