What an explorer shows
What you can look up
Three kinds of thing, and each answers different questions.
A transaction
Paste a transaction hash and you see sender, recipient, amount, fee, timestamp and how many confirmations it has collected.
An address
Paste a wallet address and you see its current balance and its entire transaction history, going back to first use.
A block
Less commonly needed, though it shows every transaction included and which validator produced it.
How to read a transaction page
Four fields carry almost all the useful information.
Status
Success, pending or failed. A failed transaction still consumed its gas, which surprises people.
Confirmations
How deep the transaction sits. This is what determines whether a merchant treats a payment as final.
From and to
The addresses. Check the destination against what was expected, because a transfer to the wrong address is a completed transfer as far as the network is concerned.
Value and fee
The amount moved and what it cost. A recipient seeing less than expected usually finds the explanation here.
Reading a token transfer
For token transfers, look at the token transfer section rather than the top-level value, which often reads zero because the native coin did not move.
What it cannot tell you
Who anybody is.
A public chain is pseudonymous. Addresses carry no names, and an explorer shows activity without identity. Labels do appear next to well-known addresses, and they come from the explorer’s own research rather than from the chain.
It also cannot tell you whether funds are clean. Some explorers display risk indicators, and proper screening is a licensed service described in the entry on KYT.
Which explorer to use
Which explorer for which network
Each chain has its own, and using the wrong one is why a hash sometimes appears not to exist.
- Bitcoin: mempool.space, blockchain.com
- Ethereum: Etherscan
- TRON: Tronscan
- Solana: Solscan, Solana Explorer
- BNB Chain: BscScan
- TON: Tonscan, Tonviewer
Multi-chain explorers exist and cover the common networks in one interface. For occasional checking they are convenient; for anything detailed the chain’s own explorer shows more.
Why a merchant uses one
One scenario, and it recurs constantly.
A customer says they paid and the order has not updated. The merchant asks for the hash, opens it in the explorer, and thirty seconds later knows which of four things happened: still confirming, wrong network, short amount, or never sent.
A payment gateway does this automatically, matching transfers to orders and recording the hash against each payment. The explorer remains the tool for anything a human needs to check by hand, and the setup guide covers where that fits.