How to read a swap transaction on a block explorer to see what went wrong

05 September 2026

The swap transaction failed, or the funds never arrived. Paste the transaction hash into a block explorer for that chain and look at the Status field first. If it says "Fail" or "Reverted", the transaction did not execute; if it says "Success" but you have no tokens, the problem is elsewhere.

Step one: confirm the transaction exists

Open the block explorer for the chain you used. Ethereum uses Etherscan, BNB Chain uses BscScan, Solana uses Solscan, and so on. Paste the transaction hash (the long string that starts with "0x" on EVM chains). If the explorer says "Transaction not found", the hash is invalid or the transaction never reached the mempool. That can happen if you copied a partial hash or the network dropped the tx. Check your wallet's history for the correct hash.

Step two: read the Status field

On EVM explorers, the status is clearly labelled near the top. "Success" means the transaction was included in a block and the smart contract executed. "Fail" means the contract reverted. Click the "Click to see more" or "View More" link to see the Revert Reason - a short error message like "insufficient output amount" or "transfer amount exceeds balance". These messages are often cryptic but point at the root cause: slippage too low, insufficient liquidity, or a token that blocks transfers.

On Solana, look for "Status: Success" or "Status: Error". Click on the instruction logs. A line like "Program log: Error: InsufficientFunds" tells you the swap failed because the pool had too little liquidity for your trade.

Step three: check the token transfers

Scroll to the Token Transfers or Logs section. This shows exactly which tokens moved in and out of your wallet. For a successful swap, you should see your input token debited and the output token credited. If only the input token moved (debited) and nothing came back, the swap failed - but sometimes the explorer still shows the debit because the contract approved the token before failing. If you see the output token credited but to an address you do not recognise, you may have been sending to a scam address, not the exchanger.

Compare the "To" address in the transfer log against the address you intended to use. If they differ by even one character, you sent funds to a lookalike address. That is a common attack. The transaction may show "Success" because the scam contract accepted the token, but you will never get the output.

Step four: inspect the method call

On EVM explorers, the Method or Function field tells you which contract function was called. A legitimate swap should call something like swapExactTokensForTokens or swapExactInputSingle. If you see transfer, approve, or multicall with no swap function, the transaction did something else. Some scams use approve to drain your allowance later. If you see a function you do not recognise, look it up on the explorer's verified contract page.

Step five: check the block timestamp

The transaction's block timestamp shows when it was mined. If it took much longer than usual, the network may have been congested, or you set a gas price too low. That alone does not break a swap, but a delayed transaction can fail if the price moves past your slippage tolerance before it confirms.

When to read the hub page

If you have traced the transaction and still cannot see what went wrong, the next thing to read is the hub page "Swapping crypto safely". It lists the checks worth making before sending funds to any exchange address, and walks through what to do when a swap fails without an obvious error.

Back to exchange fees