This article is for anyone using the MetaMask software wallet (extension or mobile) who sees errors like transaction failed metamask, warning error encountered during contract execution metamask, transaction confirmed but not in wallet metamask, or state tx is not supported metamask. I’ve been using MetaMask daily for months and have fixed many stuck transactions by following the checks below. You will get step-by-step actions and links to deeper guides like stuck pending transactions and ledger troubleshooting.
And always keep a screenshot or tx hash before trying fixes.
This is a generic wrapper. A transaction can "fail" for several reasons: out-of-gas, a smart contract revert, insufficient ETH for gas, or sending to the wrong chain. How to proceed: check the block explorer for "status: failed" and the gasUsed value. If gasUsed > 0 it hit the contract and reverted (you still paid gas). If gasUsed = 0 the tx likely never left your node or was rejected locally.
Example: I once sent a swap with a tight slippage and the contract reverted. The explorer showed a revert reason and the cure was to raise slippage slightly and re-submit.
This means the contract reverted during execution. The wallet surface displays the warning because the node returned an EVM revert. Steps:
What if no revert reason appears? Some contracts intentionally strip reasons. In that case, try a small test call or consult the dApp documentation.
This is the chain telling you the contract threw an exception (require/throw). The fix is to verify the input and state assumptions the contract expects. For example, a lending protocol will throw if your collateral ratio is too low.
This message is less common. It often points to RPC node limitations or hardware wallet translation issues (the node or hardware doesn’t recognize a requested state-related call). Fixes:
Hardware wallets introduce another layer (the device firmware and contract-data settings). Typical causes:
Fix: open the device Ethereum app, ensure firmware/app are updated, and follow connect-ledger and ledger-troubleshooting. But be careful with blind signing — only enable for trusted dApps.
(Exact UI labels change across releases; the steps above map to MetaMask’s general flow.)
Warning: resetting your account in MetaMask clears local history but does NOT remove a pending tx from the network. See reset remove for recovery tips.
| Feature / Variant | Desktop extension | Mobile app | With Ledger attached |
|---|---|---|---|
| Quick Speed Up / Cancel | Yes (UI buttons) | Yes (transaction detail) | Yes (but hardware confirmation required) |
| Edit Nonce | Yes (advanced) | Limited | Yes (via MetaMask + device) |
| dApp Browser / WalletConnect | dApp integration via injected provider | Built-in dApp browser + WalletConnect | Works, requires device app open |
Useful links: gas fees and EIP-1559, transaction error debugging, stuck pending transactions, revoke approvals.
But do not disable security features to make a specific transaction easier. Trust me, I learned that the hard way.
Q: Is it safe to keep crypto in a hot wallet if transactions keep failing?
A: A hot wallet is fine for day-to-day DeFi interactions, but repeated failures are an operational issue, not a security one. If failures are caused by malicious approvals, follow revoke approvals and consider moving funds to a hardware wallet.
Q: How do I revoke token approvals after a failed transaction?
A: Use the dApp that manages allowance revocations or a reputable revocation tool (see revoke approvals). Always verify contract addresses manually.
Q: What if a transaction is "transaction confirmed but not in wallet metamask"?
A: Check the tx hash on the explorer. If the chain shows success but MetaMask UI doesn’t, try switching networks, re-adding the token, or using reset remove. If balances still wrong, reopen the app or reinstall extension (after secure seed backup).
Q: I see "state tx is not supported metamask" — what should I do?
A: Switch RPC endpoints and update hardware firmware. If the error persists, test with a simple ETH transfer to confirm base functionality, then retry the contract interaction.
Transaction errors are frustrating but fixable with a methodical approach: get the tx hash, check the block explorer, read the revert/gas details, and then either speed up/replace or correct inputs and re-submit. If you use a hardware wallet, double-check device settings and firmware. For hands-on guides see transaction error debugging, stuck pending transactions, and ledger troubleshooting.
If you want a concise checklist PDF or step-by-step screenshots for mobile vs desktop, check the related guides: install-extension, install-mobile, and connect-ledger.
Ready to fix a specific tx? Grab the tx hash and start with the block explorer — that one move answers most questions.