⚠ Educational content only — not financial / investment / legal / security advice. On-chain transactions are irreversible. A block explorer is read-only: no genuine explorer ever needs your wallet connected or a signature to show you a result. Full disclosure → disclaimer.

Terminology first, because the names get used loosely. The tool is a block explorer — you will also see "blockchain explorer," "chain explorer," or just "the scan site." They all mean the same thing: a website that publishes every transaction, address, and block on one chain so anyone can look them up. On Ethereum the default is Etherscan. Every other chain has its own, and if you work across several chains, an aggregator such as OKLink puts them behind one search box. The layouts differ; the fields barely do.

It is not a specialist tool. In Etherscan's own words, printed at the foot of every transaction page: "A transaction is a cryptographically signed instruction that changes the blockchain state. Block explorers track the details of all transactions in the network." The data is public by construction. No login, no wallet connection, no payment.

When you actually need to open one

Nobody needs to read explorers daily. But in these situations, not reading one leaves you refreshing a wallet and guessing:

• A withdrawal has not shown up. The exchange says "completed," your wallet says nothing. The exchange gives you a transaction hash; paste it into an explorer and within seconds you know whether the funds left, and where they went. For the full withdrawal sequence and the address checks that go with it, pair this with our guide on withdrawing from an exchange to your own wallet.
• Something arrived, or left, that you did not expect. Open that transaction and you get the sender, the method it called, and the exact amount on one screen. Forgotten action or genuine problem — the page settles it.
• A swap returned less than you were quoted. You expected 200 tokens and received 195. Slippage, fees, and the route it took are all recorded; you just have to know which part of the page they are recorded in.
• You need something to show support. When you open a ticket or reconcile with a counterparty, a transaction hash beats a screenshot every time. Screenshots can be edited. A hash either resolves or it doesn't.

The screenshot records a public Ethereum page for a 0.1 ETH transfer, dated August 2026. Use the complete transaction link rather than an abbreviated hash. It includes a Delegated Address field, so it is not an example of an account without delegation state.

The eight fields that matter

Open a transaction and there is a row of tabs at the top. The ETH transfer page above shows Overview / State / API. Transactions with internal calls or event logs may also show Internal Txns and Logs (N); these can help you trace a swap, and we come back to them. Under Overview there is first a TRANSACTION ACTION line that summarises the transaction in one plain sentence. On mine it read "Transfer 0.1 ETH to 0x25FeB791…f512417d6." Read that line first, then work down the fields.

1. Transaction Hash — the ID for this one transaction

A 66-character string starting 0x. It is a fingerprint computed from the transaction's contents, unique across the chain. The practical takeaway is one line long: when you need to prove anything to anyone, give them the hash.

When a hash returns nothing, it is nearly always one of three things: characters lost in copying, a transaction that was never broadcast, or — most often — you are searching the wrong chain. A hash only means anything on the chain it was mined on. Pasting an Ethereum mainnet hash into a BNB Chain explorer returns an empty result, and that empty result tells you nothing about your funds.

2. Status — Success is not the same as "it worked"

Three values: Success (green tick), Fail, and Pending. It is the first row to read and the one people stop reading too early.

Two things about it are counter-intuitive. First, a failed transaction still costs you the fee. Fail does not mean "nothing happened"; it means the network executed your instruction and then reverted it. Validators did the work, so the gas is spent and it is not coming back. Second, Success is a statement about the chain, not about your intentions. Send funds to an address you do not control and the chain records a perfectly successful transaction. The pitfalls section below is mostly about this gap.

3. Block and Block Confirmations — how much longer

Block is the block your transaction was included in, with a confirmation counter next to it. At the moment of my screenshot it read block 25816711 and "34 Block Confirmations"; when the transaction first landed, that counter showed 2. Confirmations usually increase as new blocks arrive, but a reorganisation can change the count or temporarily remove an unfinalized transaction from the canonical chain. For crediting funds, check the platform’s requirements and the chain’s finality as well.

This row has one very concrete use: exchanges and bridges usually credit you only after N confirmations. Reading this row tells you how many more you need, which is faster and more reliable than asking support. For scale, Ethereum mainnet block numbers were in the 25.8-million range in August 2026 — a magnitude, not a fact to memorise, since a new block arrives every few seconds.

4. Timestamp — quote the UTC one, not "6 mins ago"

The row gives you both forms at once. Mine showed "6 mins ago" alongside "Aug-23-2026 08:38:35 AM +UTC."

For a quick glance, relative time is fine. But the moment you are reconciling records, filing a report, or building a timeline with a platform, use the absolute UTC value and convert to your own zone yourself. Relative time changes every time the page is refreshed, which makes a screenshot of it worthless as evidence.

5. From and To — To is not always the recipient

For an ordinary Ethereum transaction, From identifies the outer sender, usually also its fee payer. Smart accounts, bundlers, sponsorship and delegation require inspecting execution too; the sender is not always the end user. To is the direct target, not necessarily the eventual token recipient.

One habit worth breaking while you are here: checking only the first and last few characters of an address. Vanity addresses can be generated to order, so an attacker can produce one whose first four and last four characters match the address you use — identical at both ends, different in the middle, which is exactly what a four-character glance cannot catch. Compare the entire string character by character, or put the two strings on top of each other and line them up.

Hitting the copy button does not replace that check. Copying only guarantees you did not mistype; it says nothing about whether the address itself is the right one. An address dug out of the transaction history, or a payment address someone sent you that you have not confirmed through another channel, does not become trustworthy because the copy succeeded. Take the destination address from a source you trust — the counterparty's official channel, or the address book in your own wallet — and still compare the full string before you send.

6. Value — native coin only; your USDT is not in here

My transaction showed Value as "0.1 ETH ($242.11)." The distinction to hold on to: Value is only the native coin carried by the transaction — ETH on Ethereum. Send USDT, USDC, or any other ERC-20 and this row usually reads 0 ETH, because the token amount is recorded in the Token Transfers section instead. "I definitely sent 500 USDT, why does it say zero" has exactly this answer.

The screenshot shows 0.1 ETH and $242.11 in both the summary and Value row. Fiat pricing is an explorer reference, not the settlement unit. A quote seen at another time is not evidence of overpayment or missing receipt.

7. Transaction Fee and Gas Price — what it actually cost

That transfer cost 0.000043814896477448 ETH, which the page rendered as roughly $0.11, at a Gas Price of 2.074765436 Gwei. Gwei is simply a small unit of ETH — one billionth — used for gas pricing because writing gas prices in ETH means counting zeros after the decimal point.

For this execution fee, multiply gas used by effective gas price. A simple ETH transfer commonly starts at 21,000 gas, but this screenshot shows 21,118 and a delegation field. Do not assume every transaction carrying ETH uses exactly 21,000. Other networks may itemize data fees too.

Worth checking when a fee feels high (was it your bid, or was the whole network expensive?), after a failed transaction (to see what it cost you anyway), and in hindsight, if you suspect you keep transacting at the busiest hours.

8. Nonce — first suspect when nothing moves

Nonce appears in Other Attributes after expanding the details. It orders account transactions but is not a successful-transfer count: included failures consume it too, and EIP-7702 authorization processing can increment it. The screenshot’s 809 is a field example.

Because nonces execute strictly in order, a transaction with nonce 100 that underbid on gas and never got picked up will block nonce 101 and 102 behind it, however urgent they are. The standard fix is to resend at the same nonce with a higher fee so the new transaction replaces the old one. We cover that operation, and slippage settings, in the on-chain swap walkthrough, so it is not repeated here.

The layer behind More Details

Below the default fields is a row labelled More Details with a "Click to show more" prompt beside it. Expanding it adds seven or eight rows you can ignore day to day and cannot troubleshoot without. Here is what my transaction actually contained:

Input Data is the data attached to the transaction. Even with empty 0x, a target contract’s receive or fallback function can run, and a delegated account can execute code. Work out what happened from the target code, delegation, execution trace and actual asset changes together. An approval transaction usually carries hexadecimal data that Etherscan can decode, when recognised, into a method such as approve and its allowance argument. For what that allowance means, read our guide to token approvals and how to revoke them.

One footnote on Burnt: EIP-1559, live since 2021, split Ethereum's fee into a base fee that is destroyed and a tip that goes to the validator. So every transaction you send permanently removes a sliver of ETH from supply, and the flame icon on the page is counting exactly that.

Finally, the tabs. Contract interactions add Internal Txns and Logs (N): the first holds transfers triggered inside a contract, which are not standalone transactions and therefore never appear in an address's transaction list; the second holds the events the contract emitted. How many tokens you actually received from a DEX swap is answered in Logs, not in Value — which is why so many swap reconciliations fail on the first attempt.

Reading an address page: balances, labels, IN and OUT

Paste an address instead of a hash and you get an address page. I used the USDT contract address (0xdAC17F95…3D831ec7) as the example, because it is one of the most looked-up addresses on Ethereum and its page has every card populated.

Start with the word in the page header: Address or Contract. Contract means you are looking at a smart contract, not somebody's wallet. That single word is unusually useful for beginners: if you are about to send funds to a person and the header says Contract, stop and re-check where you got that address.

The row of labels under the header is the most misread element on the page. This address carries "Tether: USDT Stablecoin," "Source Code," "# Tether," "# Blocked," "# Stablecoin," and "Token Contract." Remember what those are: annotations Etherscan maintains, not chain data. On-chain there is only a hex string; names do not exist there. For what a specific marker such as "# Blocked" means, go by Etherscan's own documentation rather than assuming it means "this address is bad." The inverse holds too: an unlabelled address is not suspicious, and a reassuring label is not an endorsement.

Then three cards:

• Overview: the native ETH balance, its fiat value at the price shown, and Token Holdings (total value and how many tokens). Native balance and token holdings are separate. An ordinary account paying its own transaction fee needs enough ETH for gas. Sponsored transactions, smart accounts and transfers initiated by an already authorised third party work differently, so zero ETH does not guarantee tokens cannot leave the address.
• More Info: contract creator, creation time, token tracker, and so on. This address shows its creator as "Bitfinex: Deployer 5," created a little over eight years ago. Same caveat: that name is a label; the raw chain data is an address.
• Multichain Info: where the same string of characters shows up on other chains — mine reported "17 addresses found via Blockscan." This points at something you should internalise early: one EVM address exists on Ethereum, BNB Chain, Arbitrum and Base simultaneously, but the balances and histories on each are completely independent. So any cross-chain operation needs two explorer tabs open, one for the source chain and one for the destination; watching only one side guarantees you miss something. We collected the rest of those traps in the cross-chain bridge guide.

Below the cards sits another row of tabs: Transactions / Internal Transactions / Token Transfers (ERC-20) / NFT Transfers / Contract / Events / Analytics and more. To check whether USDT or another token arrived, start with Token Transfers. Transactions lists ordinary transactions involving the address, both incoming and outgoing; use From, To and IN/OUT to distinguish direction. Check Token Transfers for token movements and Internal Transactions for internal calls.

The list header reads Transaction Hash / Method / Block / Age / From / To / Amount / Txn Fee, and every row is flagged IN or OUT so direction is unambiguous at a glance. The Method column names the function each transaction called — Transfer, Approve, Swap and so on — and scanning that one column tells you what an address has been doing far faster than opening rows one at a time.

Last, read the small print above the list. On that address it said "Latest 25 from a total of 361,787,652 transactions" — you are being shown the most recent 25 by default. To find something from three months ago you page back or use the Advanced Filter to narrow by criteria. Not seeing a transaction in the first screen is not evidence it does not exist.

Three ways people read the page and still get it wrong

Knowing the fields is not sufficient. These three account for most wrong conclusions:

1. Status says Success and the wallet is still empty. Work through it in this order. (1) Wrong chain — you are searching an Ethereum explorer while the funds actually moved on Arbitrum or BNB Chain; switch to that chain's explorer, or use a multi-chain explorer and change networks. (2) Wrong page — incoming tokens live under Token Transfers, as above. (3) Wrong token — identically named tokens are everywhere, so compare contract addresses, never names. (4) Wallet has not indexed it — chain and address are right, the wallet just is not displaying that token; add the contract address manually and it appears. Four checks will localise nearly every case.
2. Pending and not moving. Check first whether there is a gap in your nonce sequence, then compare the gas price you paid with what the network was charging at the time. The two interact, as the nonce section explained; the speed-up and replace mechanics are covered in the swap walkthrough. One rule here: do not send a fresh transaction because you are impatient — that usually just adds another one to the same queue.
3. Treating a label as verification. "Bitfinex: Deployer 5" and "Tether: USDT Stablecoin" are conveniences supplied by the explorer. They are not on-chain facts and they are certainly not endorsements. To judge whether a transaction is suspicious, go back to the fields the chain actually recorded: From, Method, Input Data.

One search box, several chains: where an aggregator explorer helps

If everything you do happens on Ethereum, Etherscan alone is enough and you can skip this section. The friction starts the moment you are multi-chain. Every chain has its own explorer on its own domain, each with its own layout, and the question you are usually asking — "which chain did this actually go to?" — is precisely the one that forces you to open four tabs and search the same string in each. That is what an aggregator such as OKLink is for: one entry point across chains.

Opening it in August 2026, the page positions itself as an "Intelligent Web3 data platform," subtitled "Explorer, data analytics, and service provider." The genuinely useful part is the single search box, whose placeholder spells out what it accepts: an address, a transaction, a block, or a token. Four object types, one field — paste and go, with no need to pick a type first.

Below it is a multi-chain section carrying one card per chain. The cards I saw covered Bitcoin, Ethereum, X Layer, Solana, TRON and BNB Chain, each with summary figures such as market cap, 24-hour on-chain volume, average gas price or active addresses. The heading over that section read "One explorer, 40 chains" — their claim, as displayed on that date. Treat the coverage list as whatever the site shows when you open it, from the home page and the Explorer dropdown in the navigation; these lists gain and lose chains, so it is not a number worth committing to memory.

Two honest notes on the experience. The home page throws a marketing modal and a cookie bar at you; dismiss both and it works fine. And the interface is busier than Etherscan's, so reaching a specific field takes a little more scrolling. What it is not is a different set of facts. The fields map one-to-one onto what you have already learned — hash, status, block, fee — so learning either tool teaches you the other.

Which leads to a principle worth keeping: changing explorer does not change the chain. The same transaction should yield the same conclusion wherever you look it up. If two explorers appear to disagree, the first hypothesis is that you searched the wrong chain or pasted a truncated hash — not that one of them is lying to you.

A five-step routine for checking any transaction

---

FAQ · the five questions people ask

Sources cited

1. Etherscan Information Center (tutorials and field documentation) · info.etherscan.com
2. Etherscan (source of the field values recorded in this article) · etherscan.io
3. Ethereum documentation · Gas and fees (21,000 gas, base-fee burn) · ethereum.org/en/developers/docs/gas/
4. EIP-1559: Fee market change for ETH 1.0 chain · eips.ethereum.org/EIPS/eip-1559
5. EIP-7702: Set Code for EOAs (the origin of the Delegated Address row) · eips.ethereum.org/EIPS/eip-7702
6. OKLink block explorer · oklink.com

Every hash, address, block number, fee and fiat conversion quoted above is what the page displayed on 23 August 2026, and is used only to illustrate what each field means. Prices, gas prices, block heights and confirmation counts all keep moving — trust what your own screen shows you.

For unexplained transfers, save the full hash and follow the evidence checklist.