How to Clear MetaMask Cached Pending Transactions on Desktop

04 November 2026

Pending transactions in MetaMask that never confirm can get stuck in the wallet’s local cache, blocking new transactions and showing incorrect statuses. Clearing the cache forces MetaMask to re-sync with the blockchain, removing stale pending entries without affecting your funds or account history. This guide explains why pending transactions get stuck, when clearing the cache helps, and the exact steps to do it on desktop.

Why pending transactions get stuck

A transaction becomes pending when it is broadcast to the network but not yet mined into a block. Normally, it either confirms or fails. Stuck pending transactions occur when:

• Low gas price: The network is congested, and miners ignore the transaction because the gas price is too low.
• Nonce conflict: You send a transaction with a nonce that is already used by a pending transaction, creating a queue that blocks later transactions.
• Network issues: The RPC endpoint (the node MetaMask connects to) goes down or becomes slow, so MetaMask never learns whether the transaction confirmed.
• Wallet state mismatch: MetaMask’s local cache shows a transaction as pending, but the blockchain already processed it (or it never existed).

Clearing the cache removes MetaMask’s local memory of these transactions. The wallet then re-fetches the true state from the blockchain, so any confirmed transactions appear correctly, and unconfirmed ones disappear. Your ETH and tokens are not lost - they remain on-chain.

When to Clear the Cache

Clearing the cache is a safe, non-destructive fix for these situations:

• A pending transaction has been stuck for hours or days, and you cannot send new transactions.
• MetaMask shows a transaction as pending, but you know it already confirmed (check on a block explorer like Etherscan).
• You see a "queued transaction blocking new transactions" error (covered in a separate article on this site).
• The "nonce too low" error persists after you tried other fixes.

Do not clear the cache if you have a transaction that is still actively pending and you want to speed it up. For that, use MetaMask’s built-in "speed up" or "cancel" feature (available in the activity tab).

Step-by-Step: clear cache in metamask desktop

These steps work for the MetaMask browser extension (Chrome, Firefox, Brave, Edge). The mobile app uses a different reset method.

1. Open MetaMask and unlock your wallet.
2. Click the three-dot menu in the top-right corner of the MetaMask popup window.
3. Select "Settings" from the dropdown menu.
4. Go to "Advanced" in the left-hand sidebar.
5. Scroll down to the "Clear activity tab data" section.
6. Click the "Clear activity tab data" button. A confirmation popup will appear.
7. Click "Clear" to confirm.

MetaMask will now reset its local transaction history. The activity tab will go blank, then repopulate with the correct data from the blockchain. Pending transactions that were never mined will disappear. Any confirmed transactions will reappear with their final status.

What this does and does not do

• Does clear: Local cache of transaction statuses, pending queue, and activity tab history. MetaMask re-syncs from the current block.
• Does not clear: Your seed phrase, private keys, password, account addresses, imported accounts, custom tokens, network settings, or any funds. Your wallet is fully intact.
• Does not affect other wallets: If you have multiple MetaMask accounts (or multiple extensions), each must be cleared separately.

Alternative: Reset the Entire Account (More Aggressive)

If clearing the activity tab does not fix the issue (rare), you can reset the account. This is more thorough but also safe.

1. In Settings > Advanced, scroll to "Clear activity and nonce data."
2. Click the button and confirm.

This resets the nonce counter and transaction history. Afterward, MetaMask will treat your account as if it has never sent a transaction. You can then send new transactions with nonce 0 (or the next available nonce). Use this only if clearing activity tab data failed, because it removes all transaction records from the wallet’s view.

What to Do If Clearing the Cache Doesn’t Work

If pending transactions still appear after clearing the cache, the issue is likely on the network side:

• Check the transaction on a block explorer: Enter your wallet address or transaction hash on Etherscan (or the relevant chain explorer). If the transaction is not found, it was never broadcast. If it shows as pending, the network is congested, and you need to replace it with a higher gas price.
• Use MetaMask’s speed-up or cancel: In the activity tab, click the pending transaction. Options to speed up (resend with higher gas) or cancel (resend with zero value and higher gas) appear. Cancel requires a small gas fee.
• Switch RPC endpoint: Go to Settings > Networks > (your network) and change the RPC URL to a different provider (e.g., from Infura to Alchemy or a public node). Then clear the cache again.

Preventing stuck pending transactions

• Set realistic gas prices: Use MetaMask’s "Market" or "Aggressive" options during congestion. For important transactions, check gas trackers.
• Avoid rapid successive sends: Wait for one transaction to confirm before sending another, unless you are deliberately using nonces.
• Keep MetaMask updated: Outdated versions may have bugs that cause sync issues.

Clearing the cache is a quick, low-risk fix that resolves most stuck-pending problems on desktop. If it fails, the root cause is likely network congestion or a gas price issue, not the wallet itself.

Back to metamask