How to speed up a stuck transaction on MetaMask using nonce override?

Understanding Transaction Stuck States

1. A transaction becomes stuck when it remains in the pending state for an extended period without confirmation.

2. This commonly occurs due to low gas price settings relative to current network congestion levels.

3. Ethereum’s sequential nonce system prevents out-of-order execution, so a pending transaction with a lower nonce blocks all subsequent ones from that sender address.

4. The stuck condition is not caused by wallet malfunction but by the underlying EVM execution rules and mempool behavior.

5. Users often misinterpret the issue as a MetaMask bug, while it is fundamentally a protocol-level constraint tied to account state management.

Nonce Mechanics in Ethereum Accounts

1. Every Ethereum transaction carries a nonce — an incremental counter starting from zero for each external account.

2. The nonce must match the exact next expected value; any deviation results in rejection by nodes.

3. When a transaction fails or gets dropped, its nonce does not auto-increment, leaving a gap in the sequence.

4. Subsequent transactions using higher nonces are ignored until the missing one is either mined or replaced.

5. This strict ordering enforces deterministic state transitions but introduces user-facing friction during volatile gas markets.

Manual Nonce Override Procedure

1. Open MetaMask and navigate to the “Activity” tab to locate the stuck transaction.

2. Click the three-dot menu next to the pending entry and select “Speed up” — this triggers an internal override flow.

3. MetaMask automatically increments the nonce and pre-fills a new transaction with elevated gas price suggestions.

4. Adjust the gas fee manually if needed, ensuring it exceeds the previous transaction’s gas price significantly.

5. Confirm the replacement transaction — the original pending one will be invalidated once the new one propagates and confirms.

Advanced Recovery via Custom Nonce Entry

1. Access MetaMask settings and enable “Advanced” mode under the “Privacy & Security” section.

2. Return to the send interface and click “Edit” on gas settings to reveal the “Nonce” field.

3. Calculate the correct replacement nonce: it must equal the current account nonce, retrievable via Etherscan or web3.eth.getTransactionCount().

4. Enter the precise numeric value — entering an incorrect nonce causes immediate failure with “invalid sender” or “wrong nonce” errors.

5. Submit the custom transaction with sufficiently high gas to ensure inclusion in the next block.

Frequently Asked Questions

Q: Can I cancel a stuck transaction without sending a replacement?Yes. Submit a zero-value transaction to your own address with the same nonce and a higher gas price. This consumes the slot without transferring assets.

Q: What happens if two transactions with the same nonce confirm simultaneously?Only one will be included in the canonical chain. Miners select the version with higher gas fee; the other is discarded as invalid.

Q: Does resetting my MetaMask account affect my tokens or NFTs?No. Resetting only clears local transaction history and resets the nonce counter. Your assets remain secured by your private key on-chain.

Q: Why does MetaMask show “underpriced transaction” after clearing cache?This error appears when IndexedDB retains stale transaction records causing nonce desynchronization. Clearing site data restores alignment between local state and blockchain reality.