How to Read a Block Explorer

What a transaction hash is

A transaction hash, also called a TXID, is a unique fingerprint of a transaction's contents. It is created when the transaction is signed and broadcast, so it exists before confirmation. It is safe to share: it reveals only what is already public on the chain.

The fields that matter

• Status — pending/unconfirmed, success, or failed. Failed still consumes a fee on account-based networks.
• Confirmations — how many blocks have been built on top of the one containing your transaction. More confirmations means more finality.
• Block height and timestamp — when it was included.
• From and to — sender and destination. Compare the destination character by character with the address you intended.
• Amount and asset — check that a token transfer shows the token you expected, not just the network's coin.
• Fee — what was actually paid. Compare it with current conditions when diagnosing a stuck transfer.
• Memo, tag or input data — where present, the extra identifier or contract call details.

A hash only resolves on an explorer for the network it belongs to. 'Not found' often just means you are on the wrong chain's explorer.

Checking an address instead of a transaction

1. Paste the address into the explorer search box.
2. Read the current balance — this is the chain's view, independent of any wallet app.
3. Scan the transaction list for the transfer you expect, by amount and timestamp.
4. For token balances, open the explorer's token tab: tokens are separate from the native coin balance.
5. Treat unfamiliar incoming dust transfers as untrustworthy and never copy addresses out of your own history.

Reading an Ethereum or EVM transaction

Account-based networks such as Ethereum and the EVM chains show several fields Bitcoin does not, and the extra fields are where most confusion starts.

• Status — success or fail. A failed transaction still consumed gas and still appears on the chain; the fee is not refunded.
• Block and confirmations — the block that included it, plus how many blocks came after. Explorers usually also show a finalized indicator, which is the stronger guarantee on a proof-of-stake network.
• From and to — on a plain transfer, 'to' is the recipient. On a contract interaction, 'to' is the contract, and the recipient of any token appears further down instead.
• Value — the amount of the network's own coin sent. A token transfer usually shows a value of zero here, because the tokens move inside the contract rather than as the native coin.
• Transaction fee, gas used and gas price — gas used is the work performed, the effective gas price is what each unit cost, and the fee is the two multiplied. A gas limit far above gas used is normal; you are charged for what was used.
• Nonce — the sender's transaction counter. A pending transaction with a lower nonce blocks every later one from the same address.
• Tokens transferred — the explorer's decoded list of token movements. This is where an ERC-20 or NFT transfer actually shows up.
• Interacted with / method — the contract and the function called, for example an approval or a swap. Treat an approval you do not recognise as something to investigate.
• Internal transactions — value movements triggered by a contract rather than signed directly. They are reconstructed by the explorer from execution traces, not separate transactions, so they have no hash of their own.

Input data is raw call data, not a message. Do not paste it anywhere, do not run instructions found inside it, and never treat a token name, memo or link appearing in a transaction as trustworthy — anyone can send a token with any name to any address.

Checking a token or contract on an EVM explorer

1. Open the token's page from the transaction's token-transfer row rather than from a search result.
2. Compare the contract address with the address published in the project's own official documentation. Names and symbols are not unique and are trivially copied.
3. Look for the explorer's verified-source indicator, which means the published code matches the deployed bytecode. Verification is not an endorsement or a safety audit.
4. Check the holder count and creation date for obvious mismatches with what you were told.
5. Use the explorer's approvals view for your own address to see which contracts you have granted spending permission to.

Choosing an explorer safely

• Use the explorer linked from the network's own official documentation, then bookmark it.
• Explorers are read-only. A page that asks you to connect a wallet to 'unlock', 'validate' or 'claim' anything is not an explorer.
• Different explorers for the same chain can present labels differently; the underlying data is the same.

A worked example

Suppose an exchange says your withdrawal is complete but your wallet shows nothing. You take the hash from the withdrawal record, open the explorer for that network, and find status: success, 40 confirmations, destination ending in a different four characters than your address. That single check moves the problem from 'my wallet is broken' to 'the funds went somewhere else', which is a completely different response.

Sources

• Bitcoin.org: how transactions and confirmations work
• Ethereum.org: transactions