MetaMask Wallet Transaction Failure Troubleshooting: Nonce Errors, Insufficient Gas, and Getting Stuck Transactions Unstuck

A user initiates a transaction in their MetaMask wallet—a swap on Uniswap, a token transfer, or an NFT purchase—and the transaction sits pending for hours. The wallet shows no clear error message, or perhaps it displays “transaction failed” without explaining why. Meanwhile, funds remain locked, subsequent transactions cannot proceed, and the user is left wondering whether to wait, cancel, or try again. This scenario occurs frequently enough that understanding the mechanics behind failed and stuck transactions has become a practical necessity for anyone using a MetaMask wallet regularly.

Transaction failure in Ethereum and other blockchain networks is not always a simple yes-or-no outcome. A transaction can fail at different stages: before broadcast, during the mempool wait, during execution, or after confirmation—each with different causes and remedies. The issue may stem from a nonce mismatch, insufficient gas allocation, MEV front-running, network congestion, or smart contract logic errors. Learning how to diagnose and resolve these problems requires understanding how a MetaMask wallet communicates with the blockchain, how nonces work, and when retry logic helps versus when it compounds the problem.

Why transactions fail: the nonce mechanism and sequencing

Every transaction on Ethereum and compatible networks carries a nonce, a number that tracks how many transactions an address has sent. The first transaction has nonce 0, the second has nonce 1, and so forth. This sequential numbering ensures that transactions are processed in order and prevents double-spending. A blockchain node will reject any transaction with a nonce lower than the address’s current count; it will hold a transaction with a higher nonce in the mempool until all preceding nonces are confirmed.

The MetaMask wallet calculates nonce automatically by querying the network’s last confirmed transaction count and adding one. In most cases this works transparently. However, if a transaction is pending—stuck in the mempool but not yet confirmed—and the user initiates a new transaction before the first one settles, the wallet may assign the same nonce to both. This creates a nonce collision. The blockchain will accept whichever transaction reaches it first; the second becomes invalid and fails. Alternatively, if a transaction drops from the mempool due to network reorg or expiration, a subsequent transaction may reference a nonce that has now become too low, triggering another failure.

A nonce error presents as “Transaction reverted: unknown error” or simply “failed” in the transaction history. The wallet’s local interface may not immediately explain that the problem is a skipped or duplicated sequence number rather than a gas shortage or contract issue. Diagnosing nonce problems requires checking the actual pending transactions on the network using a block explorer. Open Etherscan (or the appropriate explorer for your network), paste your wallet address, and scroll through the pending transactions. If you see two transactions with the same nonce, only one will confirm; the other will fail permanently.

Gas estimation, price acceleration, and when transactions hang indefinitely

Gas represents the computational cost of executing a transaction. The user specifies a gas limit (the maximum amount of computation a transaction is permitted) and a gas price (the fee per unit of gas, measured in Gwei). If the gas limit is set too low for the transaction’s actual complexity, execution fails and the transaction is reverted—but the gas fee is still consumed. If the gas price is set too low, the transaction enters the mempool but remains unprioritized; during periods of network congestion, it may wait indefinitely without being included in a block.

The MetaMask wallet offers three preset gas strategies: Low, Standard, and Fast. These presets calculate reasonable prices based on recent network history, but they are not adaptive to rapid price changes. If you set a transaction to “Low” during a quiet period and then congestion spikes, your transaction may fall behind hundreds of newer, higher-paying transactions. Conversely, a “Fast” setting during a quiet period may overpay significantly. For this reason, understanding how to use MetaMask gas settings effectively means recognizing when presets work and when manual adjustment is necessary.

If a transaction has been pending for more than 30 minutes without confirmation, the gas price is almost certainly too low. The solution is to accelerate the transaction by submitting a new transaction with the same nonce but a higher gas price. This replacement transaction competes on the blockchain’s priority queue. The MetaMask wallet provides a built-in “Speed Up” button in the transaction details view that automates this process: it generates a new transaction with identical parameters but increases the gas price by approximately 10–12% and resubmits it. If this still fails to accelerate, the user can manually increase the gas price further and create a replacement using the same nonce.

How MetaMask tutorial basics apply to stuck transactions

Many users learn MetaMask tutorial content covering basics like wallet creation, asset importing, and dApp connection but skip the sections on transaction management and recovery. This gap becomes apparent when a transaction hangs. The standard advice—”wait for confirmation” or “try again”—breaks down when the pending transaction blocks all subsequent transactions on that address until its nonce resolves.

The correct procedure when a transaction stalls is as follows: (1) Open the transaction details by clicking on the pending transaction in your activity history. (2) Note the nonce value displayed. (3) Open Etherscan and search for your address to verify that the transaction is indeed stuck and not simply delayed. (4) If confirmed, return to the MetaMask wallet and click “Speed Up” to accelerate it with a higher gas price. (5) If Speed Up does not appear, you can also send a minimal transaction (such as 0 ETH to yourself) with the same nonce but higher gas price using the wallet’s custom nonce field under Advanced Settings. (6) Wait for the replacement to confirm before initiating new transactions.

A critical mistake is submitting multiple replacements in quick succession. Each replacement consumes gas whether it confirms or not. If you submit three Speed Up transactions with incrementally higher prices, all three will consume fees, and only one will confirm. The others become redundant. A better approach is to wait 5–10 minutes between replacement attempts, allowing the network time to prioritize your transaction or for congestion to ease. If gas prices remain elevated after several attempts, reassess whether the transaction is necessary at its current cost.

Front-running, MEV protection, and transaction ordering risks

Beyond nonce and gas issues, a transaction can fail due to external ordering within the block itself. On decentralized exchanges such as Uniswap, a large swap may shift the price between the time the user clicks “confirm” and the time a validator includes the transaction in a block. This price movement, called slippage, can cause the transaction to revert if the final output falls below a slippage tolerance (usually 0.5% to 3% by default). The transaction consumes gas but produces no token output, appearing as a failed transaction in the wallet history.

More aggressive market participants use MEV (Maximal Extractable Value) strategies to front-run ordinary users. A bot observes a pending swap, submits a similar trade with higher gas, gets confirmed first to move the price, and then the user’s transaction executes at a worse rate—or fails entirely if slippage has moved too far. The MetaMask wallet includes MEV protection features such as Flashbots Protect RPC, which routes transactions through a private mempool rather than broadcasting them publicly. This reduces visibility to bots but does not eliminate ordering risk entirely. Using the MetaMask wallet’s built-in Flashbots integration requires enabling it in settings; by default, transactions route through the public mempool.

For DeFi transactions, mitigating this risk involves (1) setting reasonable slippage tolerance based on the token pair and market conditions, (2) using Flashbots Protect or similar MEV-resistant endpoints when available, and (3) breaking large swaps into smaller portions to reduce the price impact and attractiveness to bots. None of these eliminate MEV entirely, but they reduce exposure. If a DeFi transaction fails on the first attempt, check the failure reason on the block explorer: if it shows “Slippage” or “OUTPUT_AMOUNT_LESS_THAN_MINIMUM,” the issue is price movement, not a nonce or gas problem.

Resetting nonces and using the cancel transaction pattern

In situations where a transaction’s nonce has become permanently stuck—either because it has been pending so long that the network considers it expired, or because a replacement transaction with a higher nonce was confirmed first, orphaning the original—the wallet’s nonce count becomes misaligned with the blockchain’s actual state. The MetaMask wallet does not automatically detect and recover from this condition. The user must manually reset the nonce or send a dummy transaction to re-synchronize.

The recovery procedure is: (1) Open the MetaMask wallet settings and enable “Advanced” features if not already enabled. (2) In the wallet’s transaction page, locate the stuck pending transaction and note its nonce. (3) Construct a new transaction using the same nonce (usually via custom fields or a manual nonce input). This can be a simple transaction, such as sending 0 ETH to your own address or a dummy address, to “burn” the stuck nonce. (4) Set the gas price slightly higher than the original stuck transaction to ensure confirmation. (5) Confirm and wait for this clearing transaction to be included in a block. (6) Once confirmed, normal transaction sequencing resumes, and the wallet’s nonce count re-aligns with the blockchain.

A faster alternative in some cases is to use a different wallet to send a transaction from the same address with the next available nonce. Since the wallet operates against the blockchain directly rather than within the MetaMask wallet’s interface, it bypasses any local state mismatches. However, this requires importing the private key or using a hardware wallet across multiple interfaces, which introduces additional security considerations. For most users, the reset procedure within the MetaMask wallet itself is simpler and safer.

When to abandon a transaction versus retry

Not every stuck transaction should be salvaged. If a price limit has been exceeded, the contract has changed state, or the intended counterparty is no longer available, retrying wastes additional gas. Recognizing when to stop attempting recovery is as important as knowing how to execute it.

Abandon a transaction if: (1) The intended action has become uneconomical—for example, a DEX swap where gas costs plus slippage now exceed the token value. (2) The counterparty or market state has changed significantly; a limit order that no longer matches current prices should not be forced through. (3) The transaction has been pending for more than a few hours on Ethereum mainnet (gas prices have likely shifted enough that acceleration costs more than the original transaction’s benefit). (4) Block explorers show that the transaction was explicitly reverted by the contract, indicating a logic error that will persist on retry. In these cases, it is better to acknowledge the loss of the transaction fee (if already paid), learn from the experience, and move forward rather than chase the transaction with additional fees.

Conversely, accelerate the transaction if: (1) It is genuinely pending with low gas price, and network conditions justify the cost of acceleration. (2) The action remains valuable—for instance, a time-sensitive purchase or emergency fund movement. (3) You have confirmed via block explorer that the transaction is not reverted but simply unprioritized due to gas price. In these scenarios, increasing the gas price and submitting a replacement is a rational recovery tactic.

Best practices to prevent future transaction failures

Proactive steps reduce the frequency and severity of transaction problems. First, monitor your gas settings carefully. During high-congestion periods, use the wallet’s “Advanced Gas Control” to set a gas price that aligns with current network demand. Etherscan’s gas tracker shows real-time average, standard, and fast rates; if you are performing a non-urgent transaction, match or slightly exceed the “Standard” rate rather than rushing to “Fast.” For urgent transactions, “Fast” is appropriate. For batch operations or everyday transfers, “Low” can work if you are not time-sensitive.

Second, test with small amounts first. If you are interacting with a new dApp or contract for the first time, send a small amount to verify the flow and learn the gas costs involved. This avoids committing a large sum to a transaction path that might fail unexpectedly. Third, keep your MetaMask wallet software updated. Version 13.16.3 (as of February 2026) includes critical bug fixes and improved gas estimation; older versions may have suboptimal nonce handling or incomplete MEV protection. Fourth, avoid opening multiple transactions simultaneously if you are not confident about nonce sequencing. Submit one transaction, wait for confirmation, and then proceed to the next. This prevents accidental nonce collisions.

Finally, use hardware wallet support when managing significant funds. The MetaMask wallet supports Ledger, Trezor, and Keystone hardware wallets. Hardware integration does not prevent failed transactions, but it does protect against private key theft; if a transaction fails due to gas or nonce issues, the key compromise risk remains lower than with a browser-only setup.

Using block explorers to diagnose and learn from failures

The true diagnostic tool for any transaction failure is the block explorer. Copy your wallet address or transaction hash into Etherscan (for Ethereum), Polygonscan (for Polygon), or the relevant explorer for your network. Search for your address to see all historical transactions with full details: nonce, gas used, gas price paid, revert reason, and execution status. A failed transaction will show a red “failed” label and often include an error message such as “insufficient balance,” “execution reverted,” “out of gas,” or “nonce too low.”

These messages are the definitive source of truth. The MetaMask wallet’s local display may be less specific. For instance, if a transaction shows “failed” in the wallet but the explorer shows “revert reason: Slippage,” you now know the root cause and can adjust your slippage tolerance or gas price for the next attempt. Similarly, if the explorer shows the transaction has not been included in any block and remains in the “pending” state, gas acceleration is the appropriate remedy. Bookmark your network’s block explorer and reference it whenever a transaction behaves unexpectedly. This habit transforms troubleshooting from guesswork into evidence-based diagnosis.