How to Fix a Transaction Stuck on Pending in MetaMask Mobile

Understanding Pending Transactions

1. A transaction remains pending when it has not been included in any block on the Ethereum mainnet or compatible Layer 1 chains.

2. MetaMask Mobile displays “Pending” status when the transaction hash is broadcast but no miner or validator has confirmed it yet.

3. This often occurs due to insufficient Gas Price, especially during network congestion spikes triggered by NFT mints or DeFi protocol upgrades.

4. The Ethereum mempool acts as a real-time queue—transactions with lower Gwei values sit idle while higher-paying ones leapfrog ahead.

5. Users may mistakenly assume their wallet failed to send, when in fact the node successfully propagated the raw transaction.

Gas Price Misconfiguration

1. MetaMask Mobile defaults to “Low” or “Medium” gas estimation, which may fall below current base fee thresholds during peak usage hours.

2. At times, the estimated Gas Price shown in the UI lags behind real-time mempool conditions by 30–90 seconds.

3. Manually setting Gas Price below 25 Gwei on Ethereum mainnet during high-demand windows almost guarantees indefinite queuing.

4. Some dApp interfaces inject custom gas parameters that override MetaMask’s internal estimator—users rarely notice this silent override.

5. Legacy ETH transfers using 21000 Gas Limit are particularly vulnerable if Gas Price drops even slightly below consensus minimums.

Transaction Replacement Mechanics

1. Ethereum supports transaction replacement via nonce reuse—sending a new transaction with the same nonce and higher Gas Price invalidates the prior one.

2. MetaMask Mobile allows editing only if the original transaction remains unconfirmed and visible under “Activity” > “Pending”.

3. Users must manually toggle “Speed Up” or “Cancel” options—no automatic retry or escalation logic exists within the app.

4. Choosing “Speed Up” generates a new transaction with identical payload, incremented nonce, and elevated Gas Price.

5. If the original transaction confirms after replacement initiation, both transactions execute—though only one affects balance due to nonce enforcement.

Network Layer Conflicts

1. MetaMask Mobile sometimes routes through third-party RPC endpoints that cache stale block headers or misreport pending state.

2. Switching between networks like Ethereum, Arbitrum, or Base mid-process can cause nonce desynchronization across chains.

3. Hardware wallet integrations introduce additional signing latency—especially when paired with Ledger Live’s background sync delays.

4. Certain Android OEMs throttle background app activity, interrupting WebSocket connections used for real-time mempool updates.

5. Local time drift exceeding five seconds triggers EIP-1559 validation failures, silently rejecting transaction propagation.

Troubleshooting Common Errors

1. “Unknown error: cannot estimate gas” indicates the selected RPC endpoint rejected the eth_estimateGas call—switching to a public Infura or Alchemy endpoint resolves it in 87% of cases.

2. “Nonce too low” appears when attempting to replace a transaction without incrementing the nonce—users must verify current account nonce via Etherscan before manual resubmission.

3. “Transaction was replaced” is not an error—it confirms successful cancellation; users should check the replacement hash rather than the original.

4. “Insufficient funds for gas” may surface despite adequate ETH balance if the wallet holds ERC-20 tokens with approval locks affecting available spendable balance calculation.

Frequently Asked Questions

Q: Can I recover ETH sent to a pending transaction?ETH remains in your wallet until confirmation—no funds are debited until inclusion in a block.

Q: Why does MetaMask Mobile show “Confirmed” but Etherscan shows “Not Found”?This mismatch arises from RPC endpoint divergence—MetaMask may query a forked or delayed node while Etherscan uses canonical chain data.

Q: Does clearing MetaMask Mobile cache reset pending transactions?No—pending state resides on-chain and in the node’s mempool, not locally cached; clearing cache only refreshes UI rendering.

Q: Will a stuck transaction auto-cancel after 72 hours?No Ethereum specification defines timeout expiration—stuck transactions persist indefinitely unless replaced or dropped by node policy.