Failed Transactions
When a transaction fails, your funds remain in your wallet. Here’s how to diagnose and fix common failure causes.Understanding Transaction Failures
When a transaction fails:- Your tokens are safe — Failed transactions don’t move funds
- Gas may be consumed — Some failures still use gas
- You can retry — Usually with adjusted settings
Common Failure Reasons
Slippage Exceeded
Error: “Slippage tolerance exceeded” or “INSUFFICIENT_OUTPUT_AMOUNT” What happened: The price moved more than your allowed slippage between when you submitted and when the transaction executed. Fix:
Recommended slippage:
| Token Type | Slippage |
|---|---|
| Stable/Blue chip | 1-3% |
| Medium volatility | 5-15% |
| High volatility | 15-30% |
| New launches | 30-50% |
Insufficient Gas
Error: “Insufficient funds for gas” or “Out of gas” What happened: You don’t have enough native tokens to pay for the transaction. Fix:Insufficient Balance
Error: “Insufficient balance” or “Transfer amount exceeds balance” What happened: You tried to trade more tokens than you have. Fix:- Check your actual balance with
/balance - Reduce trade amount
- Account for any pending transactions
Price Impact Too High
Error: “Price impact too high” or similar What happened: Your trade size would move the market price significantly. Fix:Token Has Sell Restrictions
Error: “Transfer failed” or transaction reverts on sell Possible causes:- Honeypot — Token designed to prevent selling
- Blacklist — Your address was blocked by the token
- Cooldown — Token has trading cooldown period
- Max wallet — Selling would leave you with invalid amount
- Check if others can sell (community/socials)
- Review token contract on block explorer
- Check GoPlus security report
Network Congestion
Error: Transaction pending for extended time, then fails What happened: Network was too congested and your transaction wasn’t included before timing out. Fix:- Wait for network congestion to reduce
- Retry during lower traffic periods
- Some chains have peak hours — avoid those times
Contract Execution Failed
Error: “Execution reverted” or contract-specific error Possible causes:- DEX router issue
- Liquidity pool drained
- Contract paused
- Invalid token pair
- Wait and retry — temporary issues often resolve
- Try a different token pair
- Check if the DEX/token has known issues
Checking Transaction Status
To investigate a failed transaction:Transaction Still Pending
If your transaction is stuck pending:| Wait Time | Action |
|---|---|
| < 2 min | Normal, just wait |
| 2-5 min | Check explorer, may be congested |
| 5-15 min | Likely stuck or failed silently |
| 15+ min | Transaction probably failed, retry |
Recovering From Failures
After a failed transaction:- Verify balance — Your tokens should still be there
- Diagnose cause — Use this guide to identify the issue
- Adjust settings — Fix slippage, amount, or wait for conditions to improve
- Retry — Submit the transaction again
Failed transactions don’t double-spend. If you retry immediately after a failure, you won’t lose funds twice.
Preventing Future Failures
Set appropriate slippage
Set appropriate slippage
Match slippage to token volatility. Start higher and reduce if trades consistently succeed.
Check before trading
Check before trading
- Verify token security (GoPlus)
- Check liquidity depth
- Review price impact
- Confirm you have gas
Start with small amounts
Start with small amounts
Test new tokens with small trades before committing larger amounts.
Monitor gas balance
Monitor gas balance
Keep sufficient native tokens for multiple transactions.
When to Contact Support
Contact support if:- Transaction succeeded but tokens didn’t arrive
- Funds are missing after a failed transaction
- You’re experiencing repeated failures with correct settings
- You see an error message not covered here