Block explorers show a transaction as a wall of hex. This tells you what actually happened: whether it worked, what tokens moved and to whom, what it cost, and above all whether you granted a permission that is still live. Free, no wallet connection, nine chains.
What this page is for. A block explorer shows a transaction as a wall of hex. This answers the questions you actually have: did it work, what moved and where to, what did it cost, and did you give anything a permission it still holds.
The last one matters most. An approval granted inside a transaction does not end when the transaction does. It sits there until it is used or revoked, and it is how most drained wallets are drained. This page names every approval a transaction created and says whether it was unlimited.
In your wallet's activity list, open the transaction and look for a long string beginning 0x followed by sixty four characters, usually labelled hash or transaction ID. Copy it, pick the chain it happened on, and paste it above. If it says no transaction exists, the chain is almost always wrong rather than the hash: the same hash rarely exists on two chains.
A failed transaction was included in a block and then reverted, so nothing it intended to do happened. You still paid the gas because the network did the work of attempting it. Nothing else was taken from you. Common causes are slippage moving past the limit you set, an allowance that was not granted first, or a contract refusing the call. A failure is annoying and it is not a loss beyond the fee.
One transaction often moves several tokens, because a swap routes through more than one pool and each hop is its own transfer. If the list looks more complicated than what you thought you were doing, that is usually why rather than anything being wrong. Movements from or to the zero address are tokens being created or destroyed rather than sent by anyone.
A failed transaction was included in a block and then reverted, so nothing it set out to do happened. The usual causes are the price moving past the slippage limit you set, a required approval not being granted first, the contract refusing the call for its own reasons, or running out of gas. You still pay the fee because the network did the work of attempting it, but nothing else is taken from you. A failure costs you gas and nothing more.
An approval is permission for a contract to move a token on your behalf. It is granted inside a transaction and it does not end when that transaction does. It sits there until it is used up or you revoke it. That is why most drained wallets are drained: not by a technical break in, but by a permission the owner granted, often through a link, and forgot about. This page names every approval a transaction created and tells you whether it was unlimited.
It means the contract can move as much of that token as you ever hold, indefinitely, without asking again. Interfaces request it because it saves you approving repeatedly. It is convenient right up until the contract you approved turns out to be malicious or is later compromised. Approving the exact amount you intend to spend costs slightly more gas and caps your exposure at that amount.
Because a swap usually routes through more than one pool, and each hop is its own transfer. A trade you think of as one action can appear as five or six movements. Transfers from the zero address are tokens being created, and transfers to it are tokens being destroyed, rather than anyone sending anything.
Almost always the wrong chain is selected. The same hash rarely exists on two chains, so a not found result is usually the chain rather than the hash. Check where the transaction actually happened and select that chain.
No. Paste a hash. The page reads public blockchain data and nothing else, with no sign up and no wallet connection. Nothing you enter is stored.
We seal the list every week and keep re-checking every token on it, so you can see what actually happened to them rather than only what is trading today.
