A transaction that comes back marked "failed" is one of the more confusing moments for someone new to crypto. You confirmed everything, you waited, and the result is a red mark in your history. Worse, a small network fee left your wallet anyway, even though nothing actually moved.
None of this means your money is gone, and none of it means something is broken with your wallet. Failed transactions are a normal part of how the Base network works. This guide explains why they happen, walks through the most common causes, and gives you a clear next step for each one.
First, the part that surprises people: why you still pay
When you submit a transaction, the network does real work to process it. Validators run the instructions, check the conditions, and record the outcome. That work costs the same whether the transaction succeeds or fails.
So if a transaction fails partway through, the network reverses any changes it started to make, but it still charges you for the computation it already performed. That is the small fee you see leave your wallet. On Ethereum mainnet this can sting, but on Base the network fee is usually a fraction of a cent, so a failed transaction is cheap, just annoying.
The important thing to understand is what does not happen. The tokens you were trying to swap or send stay in your wallet. Only the network fee is spent. Your balance of the actual asset is untouched.
This is confirmed by wallet providers and block explorers alike. As MetaMask explains, you are paying for the computation, not for the outcome.
Common cause 1: slippage was too tight
This is the most frequent reason a swap fails.
When you swap, the price can move slightly between the moment you tap confirm and the moment the network processes the trade. Slippage tolerance is the cushion you allow for that movement. If the price moves more than your cushion permits, the network cancels the swap to protect you from a worse deal than you agreed to.
In other words, a failed swap from tight slippage is the safety net doing its job. It refused to fill your trade at a price you did not approve.
What to do: try the swap again. If it keeps failing, raise your slippage tolerance a little, for example from a very small value up to around half a percent or one percent for a normal token. Be careful here, because a very high slippage setting can expose you to a much worse price. Raise it gradually, not all at once.
Common cause 2: not enough ETH for the network fee
Every transaction on Base is paid for in ETH, even when the thing you are doing involves other tokens. If you hold a token you want to swap but have no ETH at all, the transaction cannot be processed and will fail or will not submit.
What to do: keep a small amount of ETH in your wallet at all times, purely to cover network fees. On Base this does not need to be much, because fees are low. Our guide on getting ETH onto Base covers the simplest ways to top up.
Common cause 3: the token needs an approval first
Before a wallet can swap a token, you grant a one time permission called an approval. If that step has not happened yet, or did not complete, the swap itself can fail.
Most wallets handle this for you by prompting the approval and then the swap as two steps. If a swap fails on a token you have never traded before, an incomplete approval is a likely reason.
What to do: look for an approval prompt and confirm it first, then try the swap again. If you want the full picture of what approvals are and why they matter for safety, we have a dedicated article on token approvals.
Common cause 4: a stuck or pending transaction ahead of it
Transactions from one wallet are processed in order. If an earlier transaction is stuck as pending, the ones behind it wait too. This is rare on Base because the network is fast, but it can happen during heavy congestion.
What to do: give it a few minutes. On Base, pending transactions usually clear quickly. If something stays pending for a long time, avoid spamming new transactions, since each one queues behind the stuck one. Waiting is almost always the right move.
Common cause 5: the contract rejected the action
Sometimes the smart contract you are interacting with refuses the transaction on purpose. A token might have a feature that blocks certain trades, a sale might have ended, or a condition the contract requires was not met. Block explorers often label this as "execution reverted." As Ledger notes, this message means the contract itself declined to run the action.
What to do: this one deserves caution. If a normal looking swap on a well known token reverts repeatedly for no clear reason, treat the token with suspicion. Some scam tokens are deliberately built so you can buy them but never sell. Our guide on spotting scam tokens explains the warning signs.
How to read what went wrong
You do not have to guess. Every transaction on Base, successful or failed, is recorded on a public block explorer called BaseScan. Open your transaction there and it will show the status and often a short reason for the failure.
Learning to read a transaction on a block explorer is one of the most useful habits in self-custody, because it turns a mysterious red mark into a clear, checkable fact. We have a full walkthrough on using a block explorer if you would like to learn that step by step.
The calm summary
A failed transaction is rarely an emergency. Your tokens are safe, only a tiny fee was spent, and the cause is almost always one of a short list: slippage too tight, not enough ETH for fees, a missing approval, a stuck earlier transaction, or a contract that refused the action.
Work through that list calmly, check the explorer if you want certainty, and be extra careful only in the one case that matters, a token that lets you buy but quietly refuses to let you sell.
Sources: MetaMask Help Center, Ledger Support, Etherscan Information Center