How to read a blockchain explorer: the 8 fields that tell you where your money actually went
A withdrawal that says "completed" and never arrived. A swap that paid out less than the quote. A transfer sitting in your wallet that you have no memory of making. All three questions are answered on the same screen — a block explorer's transaction page. The problem is that the first time you open one you get a wall of hex and thirty-odd labels, and most people close the tab. This guide takes apart one real Ethereum transaction exactly as it rendered in August 2026: the eight fields worth knowing, the extra layer hiding behind More Details, how to read an address page, and when a multi-chain explorer saves you time. There is a five-step checklist at the end.
⚠ 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.
Every field name and value below comes from one real transaction I opened on 23 August 2026: an ordinary 0.1 ETH transfer on Ethereum mainnet, hash starting 0xb46ccc03…f26f0831. Search it today and you will see the same screen, with a much larger confirmation count. One note on method: Etherscan has been redesigned more than once, so throughout this piece I describe rows by the label printed on them rather than by position. Button placement moves between releases; the field names have been remarkably stable.
The eight fields that matter
Open a transaction and there is a row of tabs at the top. The transfer above is a plain send, so it carries only Overview / State / API. A contract interaction — a DEX swap, for instance — adds Internal Txns and Logs (N); those two are where a swap's real numbers live, 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 only ever go up — refresh and there are more.
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
From is the address that signed the transaction and paid the gas. To needs more care: in a plain transfer, To is the recipient; in a contract interaction, To is the contract, and whoever actually received tokens appears further down in Token Transfers or Logs. Plenty of people panic at an unfamiliar To address that is simply a DEX router.
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, and address-poisoning attacks exist precisely because people compare four characters at each end. Compare the whole string, or use the explorer's copy button and paste it.
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.
A detail I checked deliberately at the time: the TRANSACTION ACTION summary at the top of the page put the dollar value at $241.16, while the Value row said $242.11. Same transaction, same screen, two different dollar figures. The reason is that the fiat conversion is a convenience the explorer adds, and different parts of the page price it at slightly different moments. The only number the chain settled is "0.1 ETH." Treat every dollar figure on an explorer as an estimate.
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.
The relationship in one line: fee = gas actually used × price per unit of gas. The Ethereum documentation puts a standard ETH transfer at 21,000 units of gas; contract calls consume considerably more, which is why a swap costs visibly more than a transfer at the identical gas price.
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
The first seven fields are visible by default. Nonce is not — it sits inside the Other Attributes row of the expanded section — but it earns its place here. The nonce is a strict counter of how many transactions this address has sent, starting at 0. Mine read 809, meaning that address had successfully sent 809 transactions before this one. It is invisible until the day it matters: a transaction stuck on Pending and going nowhere.
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:
| Field | Value on that transaction (2026-08-23) | How to read it |
|---|---|---|
| Gas Limit & Usage by Txn | 31,926 | 21,118 (66.15%) | The first number is the ceiling you (or your wallet) set; the second is what was actually consumed. The unused portion is refunded, not spent — so a generous gas limit does not mean a bigger bill |
| Gas Fees | Base: 0.074765436 Gwei / Max: 2.107570689 Gwei / Max Priority: 2 Gwei | Base is set by the protocol according to congestion and is burned; Max Priority is the tip to the validator; Max is your ceiling, and you are charged on the first two, not on this |
| Burnt & Txn Savings Fees | Burnt about 0.0000015789 ETH / Txn Savings about 0.0000006928 ETH | Burnt is the portion destroyed permanently; Savings is what you were not charged because the actual base fee came in below your Max |
| Delegated Address | a contract address starting 0x | You may see this row on some ordinary addresses. It means the address has delegated code under EIP-7702. It is not a warning sign and it does not change how you read the transfer itself |
| Other Attributes | Txn Type: 2 (EIP-1559) / Nonce: 809 / Position In Block: 66 | Type 2 is today's standard fee model; nonce as described above; Position In Block is where it sat in the block, which matters for ordering and front-running questions |
| Input Data | 0x | A plain transfer has an empty 0x here. Anything longer means the transaction called a contract, whatever the rest of the page looks like |
| Private Note | prompts you to log in | A private annotation feature that needs an Etherscan account. Looking transactions up never requires one, and nothing in this guide does |
The row worth genuinely learning is Input Data. It is the verbatim instruction the transaction handed to a contract. Empty 0x means a plain send. On an approval transaction it is a long hexadecimal blob, and Etherscan generally offers a toggle that decodes it into the method name and its arguments — you can read the word approve and the allowance amount directly. If it is not obvious to you why an allowance figure matters, read our guide to token approvals and how to revoke them, which is entirely about finding and killing dangerous ones.
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). One trap is worth knowing before you hit it: the native balance and the token holdings are unrelated. An address can hold a long list of tokens and almost no ETH — and in that state it cannot move any of them, because there is nothing to pay gas with. Beginners who send tokens to a fresh wallet and find them frozen there have almost always hit this.
- 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. Here is the highest-frequency mistake on this whole page: to check whether USDT or any other token arrived, open Token Transfers, not Transactions. Transactions lists transactions this address itself sent. Somebody sending you tokens is recorded under Token Transfers.
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:
- 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.
- 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.
- 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
Next time the question is "where did my money go," run these in order:
- [ ] Step 1 — establish the chain. Which chain did this move on? Open that chain's explorer instead of reflexively opening Etherscan
- [ ] Step 2 — paste the hash, read Status. Success, Fail or Pending settles the category. Pending sends you straight to Nonce and Gas Price
- [ ] Step 3 — verify From and To. Compare the full strings, never just the ends. A To that is a contract means this was an interaction, not a plain transfer
- [ ] Step 4 — look for the amount in the right place. Native coin in Value, tokens in Token Transfers, DEX swap output in Logs
- [ ] Step 5 — count the confirmations. Platforms credit at a threshold; below it you are waiting, not missing funds
One-line rule: chain first, status second, and only then go looking for which column the number is in. Reverse that order and you spend most of your time reading the wrong page.
FAQ · the five questions people ask
My transaction says Success but I never received the funds. What happened?
Success only means the chain executed the instruction as written; it does not promise the money landed where you expected. Check four things in order. One, the chain: the same address exists on several chains, and the funds may have moved on a different one. Two, the page: incoming tokens are recorded under Token Transfers on the address page, not under Transactions. Three, the token: identically named tokens are common, so compare contract addresses rather than names. Four, the wallet: if chain and address are both right, the wallet may simply not be displaying that token, and adding the contract address manually will reveal it. Those four checks localise almost every case.
What does nonce mean on Etherscan, and why does it matter?
The nonce is a counter of how many transactions an address has sent, starting at zero and increasing by exactly one each time. It matters because nonces execute strictly in order. If a transaction with nonce 100 underbid on gas and never gets included, every later transaction from that address queues behind it no matter how urgent they are, which is why one stuck transaction can appear to freeze a whole wallet. The standard fix is to resend at the same nonce with a higher fee so the new transaction replaces the stuck one. On Etherscan the nonce is not visible by default; expand the More Details section and look in the Other Attributes row.
Do I need an account or a connected wallet to look up a transaction?
No. On-chain data is public, so entering a transaction hash or an address is enough, with no login, no wallet connection and no payment at any point. A few extras need an account, such as Etherscan's Private Note feature, but that has nothing to do with lookups and you can read every field discussed here without it. The corollary is a safety rule: any page that claims you must connect a wallet or sign a message before it will show you a result should be closed immediately, because that is a standard phishing pattern. Reach explorers by typing the domain yourself or from a bookmark.
Can I cancel a transaction that is stuck pending?
You cannot delete one, but you can overwrite it. Transactions execute in nonce order, so a stuck nonce holds up everything behind it. The usual approach is to broadcast a replacement at the same nonce with a higher fee, typically a zero-value transfer to yourself, so it gets included first and the original becomes invalid. Most major wallets package this as a speed up or cancel button, so you rarely enter a nonce by hand. Two caveats: the replacement transaction costs gas of its own, and you should not simply send a fresh transfer out of impatience, because that usually just adds another transaction to the same queue.
Is the name shown next to an address on a block explorer part of the chain data?
No. On-chain there is only a hex string starting 0x, with no names attached. Labels such as Tether: USDT Stablecoin or an exchange hot wallet tag, along with the hashtag markers beside them, are annotations the explorer maintains and curates. They are genuinely useful for recognising well-known addresses, but keep three things straight: a label is not chain data, not an official verification, and not a safety endorsement. An address with no label is not thereby suspicious, and a reassuring label does not make an address trustworthy. To judge whether a transaction is suspicious, read the fields the chain actually recorded, such as From, Method and Input Data.
Sources cited
- Etherscan Information Center (tutorials and field documentation) · info.etherscan.com
- Etherscan (source of the field values recorded in this article) · etherscan.io
- Ethereum documentation · Gas and fees (21,000 gas, base-fee burn) · ethereum.org/en/developers/docs/gas/
- EIP-1559: Fee market change for ETH 1.0 chain · eips.ethereum.org/EIPS/eip-1559
- EIP-7702: Set Code for EOAs (the origin of the Delegated Address row) · eips.ethereum.org/EIPS/eip-7702
- 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.