Crypto Transaction Failed? Here Is Exactly What to Do in 2026 (Step-by-Step Fix)
Published on 2026-06-16
Your Transaction Failed. Do Not Panic.
You hit "Confirm" in your wallet. The transaction spins. Then it fails. Your heart rate spikes. Did you just lose everything?
In most cases, no. A failed crypto transaction usually means the transaction was reverted — the blockchain rejected it, and your funds are still in your wallet. You lost the gas fee (the cost of attempting the transaction), but the tokens you tried to send, swap, or approve are untouched.
But "usually" is not "always." Some failure modes leave your wallet in a confused state. Stuck transactions can block all future activity. Failed approvals can leave dangling permissions. And on certain chains, the error messages are cryptic at best.
This is the Anti-Loss Protocol for failed transactions: a systematic process for diagnosing what went wrong, recovering your funds (if needed), and preventing the same failure from happening again. Follow these steps in order.
Step 1: Check the Transaction on a Block Explorer
The first thing to do is look up your transaction on a block explorer. This tells you exactly what happened — not what your wallet thinks happened.
- Ethereum: etherscan.io
- Base: basescan.org
- Arbitrum: arbiscan.io
- Optimism: optimistic.etherscan.io
- Polygon: polygonscan.com
- Solana: solscan.io
- BNB Chain: bscscan.com
Paste your transaction hash (txid) or your wallet address into the search bar. Find the failed transaction and check its status:
- Status: Failed (Reverted): The transaction was attempted but reverted. Gas was consumed, but no state changes occurred. Your tokens are safe.
- Status: Pending / Queued: The transaction is still in the mempool, waiting to be included in a block. It has not failed yet — it is stuck.
- Status: Dropped / Replaced: The transaction was replaced by a newer one (same nonce) or dropped from the mempool. It will never be confirmed.
- Status: Success: The transaction actually succeeded. If your wallet shows a failure, it may be a display bug — check your wallet balance directly.
Step 2: Identify the Failure Type
Different failures require different responses. Here are the most common failure types and what they mean:
Type 1: Out of Gas
Error message: "Out of gas" or "execution reverted: out of gas"
What happened: You set a gas limit that was too low for the transaction to complete. The transaction ran until it hit the gas limit, then reverted. You paid gas for the computation that was performed before the revert.
Are your funds safe? Yes. The transaction was fully reverted.
How to fix: Retry the transaction with a higher gas limit. Most wallets auto-estimate gas, but complex DeFi interactions (multi-hop swaps, contract deployments, NFT mints during high demand) can exceed the estimate. Increase the gas limit by 20-50% and resubmit.
Type 2: "Execution Reverted" (No Details)
Error message: "execution reverted" or "VM Exception while processing transaction: revert"
What happened: The smart contract explicitly rejected the transaction. This is the most common failure type and has dozens of possible causes:
- Slippage too low: The price moved between when you submitted and when the transaction was processed. The DEX contract reverted to protect you from a worse price.
- Insufficient token approval: You tried to swap a token without first approving the DEX router to spend it.
- Insufficient balance: You tried to send more tokens than you have (including accounting for gas if sending ETH).
- Contract-level restriction: The token has a transfer cooldown, blacklist, or pause mechanism that blocked the transaction.
- Function parameter error: You entered an invalid value (e.g., zero amount, wrong token address).
How to diagnose: On the block explorer, click the "Input Data" or "Decode Input Data" button on the transaction page. This shows the exact function that was called and the parameters. If the input data shows "Error: Panic" or a custom error, the contract's documentation may explain the error code.
How to fix: For slippage errors, increase your slippage tolerance (try 1-3% for volatile tokens, 0.5% for stablecoins). For approval errors, submit an approval transaction first, then retry the swap. For insufficient balance, reduce the amount or check if you need to account for gas separately.
Type 3: Stuck / Pending Transaction
Symptom: Transaction shows "Pending" for more than 5 minutes. Your wallet shows a spinning indicator.
What happened: You set a gas price that is too low for current network conditions. Miners/validators are prioritizing higher-paying transactions, and yours is stuck in the mempool.
Are your funds safe? Yes — but the pending transaction is blocking all subsequent transactions from your wallet (because of nonce ordering). You cannot send a new transaction until the pending one is confirmed or replaced.
How to fix — Option A (Speed Up): Most wallets (MetaMask, Rabby, Phantom) have a "Speed Up" button on pending transactions. This resubmits the same transaction with a higher gas price. The higher gas incentivizes validators to include it.
How to fix — Option B (Cancel): Send a new transaction with the same nonce as the stuck transaction, sending 0 ETH to yourself, with a higher gas price. This replaces the stuck transaction with a no-op, freeing your wallet. In MetaMask, click "Cancel" on the pending transaction — it does this automatically.
How to fix — Option C (Wait): If the gas price drops (e.g., during off-peak hours), your transaction may eventually be confirmed. On Ethereum, pending transactions are dropped from the mempool after approximately 24-48 hours if never confirmed.
Type 4: Nonce Too Low / Nonce Too High
Error message: "nonce too low" or "nonce too high" or "replacement transaction underpriced"
What happened: Your wallet's nonce tracking is out of sync with the blockchain. This commonly happens after a stuck transaction, after using multiple wallets on the same account, or after importing a seed phrase into a new wallet app.
How to fix: In MetaMask, go to Settings → Advanced → "Clear Activity Tab Data" (this resets nonce tracking). Alternatively, manually set the nonce: enable "Customize Transaction Nonce" in Advanced Settings, then enter the correct nonce (check your last confirmed transaction on the block explorer and add 1).
Type 5: Insufficient Funds for Gas
Error message: "insufficient funds for gas + value" or "insufficient balance"
What happened: You tried to send tokens (or ETH) but do not have enough ETH (or the native gas token) to pay for the transaction. On Ethereum, you need ETH for gas even if you are sending USDC. On Solana, you need SOL. On Base, you need ETH on Base.
How to fix: Send a small amount of the native gas token to your wallet first. For Ethereum mainnet, $5-10 worth of ETH is enough for many transactions. For L2s (Base, Arbitrum, Optimism), $0.50-1.00 is usually sufficient. Use Crypto Network Guide to find the cheapest way to bridge gas tokens to your target network.
Step 3: Check Your Wallet State After the Failure
After a failed transaction, verify your wallet is in a clean state:
- Token balances: Check that your token balances are what you expect. A reverted transaction should not change balances.
- Token approvals: If the failed transaction was an approval, check whether the approval actually went through. Go to revoke.cash and verify. Some approvals succeed even when the subsequent swap fails.
- Pending transactions: Check that no transactions are stuck in the pending state. A stuck transaction will block future transactions.
- Nonce: Check your next expected nonce on the block explorer (under "Internal Txns" or "More Details" on your address page). Make sure your wallet's nonce matches.
Step 4: Retry (With the Right Settings)
Once you have diagnosed the issue and confirmed your wallet is in a clean state, retry the transaction with corrected parameters:
| Failure Type | Setting to Change | Recommended Value |
|---|---|---|
| Out of gas | Gas limit | Increase by 20-50% above wallet estimate |
| Slippage revert | Slippage tolerance | 1-3% for volatile tokens; 0.5% for stablecoins |
| Missing approval | Submit approval first | Approve exact amount (not unlimited) |
| Stuck transaction | Speed up or cancel | Increase gas price by 10-20 gwei |
| Nonce mismatch | Reset nonce | Clear activity data or set manually |
| Insufficient gas funds | Fund wallet with native token | $5-10 ETH for L1; $0.50-1.00 for L2 |
| Price impact too high | Reduce trade size | Split large trades into smaller chunks |
When a Failed Transaction Means Lost Funds
In most cases, a failed transaction means your funds are safe. But there are exceptions:
- Bridge transactions: If you initiated a cross-chain bridge and the transaction failed on the source chain, your tokens should still be in your wallet. But if the bridge partially executed (tokens locked on source chain but not minted on destination), you may need to contact the bridge's support. Check both chains.
- Partial fills on DEXs: Some DEX aggregators (1inch, Paraswap) use "partial fill" logic where part of your trade succeeds and part fails. You may receive some of the output token but not all. Check your token balances carefully.
- Failed contract deployments: If you were deploying a contract and it failed, the contract address may or may not exist. Check the block explorer. Gas is consumed regardless.
- Failed on one chain, succeeded on another: If you used a cross-chain messaging protocol (LayerZero, Axelar, Wormhole) and the message failed on the destination chain, your tokens may be locked in the destination chain's bridge contract. Contact the protocol's support with your transaction hash.
Prevention: The Anti-Loss Protocol for Transaction Success
Most failed transactions are preventable. Follow these rules to minimize failures:
- Check gas prices before transacting. Use Crypto Network Guide to compare current gas costs across networks. Avoid transacting during peak hours (US business hours, NFT mints, major token launches).
- Set appropriate slippage. For stablecoin-to-stablecoin swaps: 0-0.5%. For volatile tokens: 1-3%. For low-liquidity tokens: 5%+. If your transaction keeps failing due to slippage, the token may have high price impact — reduce your trade size.
- Approve before swapping. Always submit the approval transaction first, wait for confirmation, then submit the swap. Do not try to do both in one click unless you are certain the token is already approved.
- Keep a gas reserve. Always keep at least $10-20 worth of the native gas token in your wallet. Running out of gas mid-operation is the most common cause of failed transactions.
- Test with a small amount. Before making a large trade or bridge, send a small test amount. If the test succeeds, proceed with the full amount.
- Verify the contract address. Before interacting with any token, verify the contract address on CoinGecko, CoinMarketCap, or Crypto Network Guide. Interacting with a fake token contract is a common cause of reverted transactions.
- Do not set custom gas limits too low. Let your wallet auto-estimate gas unless you have a specific reason to override it. If you must set a manual limit, add a 30% buffer.
Transaction Failure Quick Reference
| Error / Symptom | Meaning | Funds Safe? | Action |
|---|---|---|---|
| Out of gas | Gas limit too low | Yes | Retry with higher gas limit |
| Execution reverted | Contract rejected tx | Yes | Check slippage, approval, balance |
| Pending for 5+ min | Gas price too low | Yes (but blocked) | Speed up or cancel |
| Nonce too low | Nonce already used | Yes | Reset wallet nonce tracking |
| Nonce too high | Skipped a nonce | Yes | Fill in missing nonce transaction |
| Insufficient funds | Not enough for gas + value | Yes | Fund wallet with native token |
| Replacement underpriced | Cancel/speedup gas too low | Yes | Increase replacement gas by 10%+ |
| Bridge failed (source) | Tokens not locked | Yes | Retry bridge or use alternative |
| Bridge failed (destination) | Tokens locked, not received | No (locked in contract) | Contact bridge support |
| Partial fill (DEX) | Part of trade succeeded | Partial | Check balances; retry remainder |
Bottom Line
A failed crypto transaction is almost always recoverable. The blockchain reverted the state — your tokens are still in your wallet, minus the gas fee you paid for the attempt. The key is to diagnose the failure type using a block explorer, fix the underlying issue (gas limit, slippage, approval, nonce), and retry with corrected settings.
The Anti-Loss Protocol for failed transactions is: check the block explorer first, identify the failure type, verify your wallet state is clean, and retry with the right settings. Do not panic-send a second transaction while the first is still pending — that is how users accidentally double-spend or get stuck in nonce conflicts.
Before your next transaction, check current gas prices and network status at Crypto Network Guide — because the cheapest transaction is the one that succeeds on the first try.