How to read a block explorer
The ledger is public. This is how you actually read it.
A block explorer is a website that reads a blockchain and shows you what is on it. Because the ledger is public, it needs no permission and no account — you paste in a transaction ID or an address and see the real state of things.
This is the skill that turns “trust me, I sent it” into something you can check yourself, and it is genuinely easy. Most people never learn it because every guide starts with a screenshot of an interface that has since been redesigned.
Finding the right explorer
Each chain has its own, because each explorer reads one ledger. Bitcoin explorers cannot see Ethereum transactions and vice versa. Your wallet almost always links to one directly from a transaction — that link is the safest route, because it avoids the other way people arrive at an explorer, which is a search result for a lookalike domain.
Explorers are read-only. A page that asks you to connect a wallet, enter a seed phrase, or sign anything to “unlock” or “validate” a transaction is not an explorer, whatever it looks like.
The anatomy of a transaction
Field names vary slightly between explorers. These are the ones that appear on nearly all of them.
| Field | What it is | Why it matters |
|---|---|---|
| Transaction hash | The transaction's unique ID, and its permanent address on the ledger. | This is what you send someone to prove a payment exists. Anyone can look it up; nobody needs an account. |
| Status | Pending, success, or failed. | A failed transaction still consumed a fee. Failure is not the same as the money coming back untouched. |
| Block / height | Which block included it, and that block's position in the chain. | Blank means it is still waiting. A number means it has been written down. |
| Confirmations | How many blocks have been built on top of the one containing it. | The practical measure of finality. More blocks means more work an attacker would have to redo. |
| From / To | The sending and receiving addresses. | Check the whole string, not the middle. Attacks rely on you checking the first four characters only. |
| Value | The amount moved. | Shown in the chain's native unit, usually with a converted figure beside it that is only an estimate. |
| Fee | What was paid to have it processed. | Set too low and it sits unconfirmed. It is paid whether or not the transaction succeeds. |
| Timestamp | When the including block was produced. | Roughly when it settled — not when it was broadcast, which is usually earlier. |
Following one through
The sequence is the same everywhere, and there are only four states worth knowing:
- Broadcast. Your wallet sends the signed transaction to the network. It now sits in the mempool — the waiting room — with every other unconfirmed transaction. The explorer will show it as pending, with no block number.
- Selected. Whoever builds the next block picks transactions from that pool, generally highest-paying first. This is why a low fee means a long wait rather than an error: nothing is wrong, you are simply outbid.
- Confirmed once. A block containing it is published. The explorer now shows a block number, a timestamp, and one confirmation.
- Buried. Each subsequent block adds a confirmation. Nothing changes about your transaction — what changes is how expensive it would be for anyone to undo it.
There is no field that says “final”, because finality is a probability rather than a state. Exchanges pick a confirmation count they are comfortable with and wait for it; the deeper it is buried, the more work an attacker would have to redo. Our Proof of Work page explains why that cost rises.
Reading an address
Paste an address instead and you get its full history: balance, every transaction it has been part of, and when it was first used. This is the part people find unsettling once they see it — an address is pseudonymous, not private. It carries no name, but everything it has ever done is permanently public, so an address linked to your identity once is linked to it for good.
Three things it is genuinely useful for
- Confirming a payment. Someone says they paid. The hash either exists with the right amount to the right address, or it does not.
- Diagnosing a stuck transaction. Pending with a low fee means wait. Failed means it ran and reverted, and the fee is gone. Not present at all means it never reached the network, so nothing was spent.
- Checking an address before you send. A contract address with no history, deployed yesterday, is worth knowing about before rather than after.
What it will not tell you
An explorer shows what happened, not what it meant. It cannot tell you who owns an address, whether a token is worth anything, or whether a transfer was voluntary. Labels attached to well-known addresses are the explorer's own annotation, not part of the chain, and they can be wrong or out of date. And activity inside an exchange never appears at all — those trades are database rows, not on-chain events.
This is a reference explainer, not financial advice. Cryptocurrency is volatile; do your own research.