Encyclopedia Ethereum · Entry 25
How to read an Ethereum block explorer
In this article
At a glance
Key facts
| Fact | Detail | Source |
|---|---|---|
| Execution status | Receipt success describes EVM execution, not the legitimacy of an asset or agreement | [2][4] |
| Token transfers | Token events and contract state differ from the transaction’s ETH value field | [5][3] |
| Execution fee | Gas used multiplied by the effective gas price | [2][6] |
Begin with the network and exact transaction
The transaction hash identifies the signed transaction record to investigate on the chosen network. Check that the explorer is showing the intended chain and distinguish pending submission from inclusion in a block. A transaction receipt is evidence about an included transaction’s execution.
An included transaction can succeed or revert. Receipt status describes that execution result. Inclusion alone does not say the block is finalized, and successful execution does not establish that the recipient is trustworthy or that an application fulfilled an offchain promise.
Example: zero ETH value with a token transfer
Imagine a transaction calls a token contract to transfer 25 tokens. Its top-level ETH value can be zero because the action moves balances recorded by the token contract, rather than sending native ETH in that value field. Calldata identifies the requested contract action.
An explorer may decode a Transfer event from the receipt logs and display the token movement. Check the emitting contract and the token’s unit convention. An event with a familiar name is not proof that it came from the asset you intended, and a displayed symbol is not a unique token identifier.
Example: calculating the execution fee
Suppose the receipt reports 50,000 gas used and an effective gas price of 4 gwei. Multiplying gives 200,000 gwei, or 0.0002 ETH. This illustrative calculation uses gas actually consumed, rather than multiplying the transaction’s maximum gas limit by a fee cap.
For a reverted included transaction, consumed execution still costs gas even though its reverted application changes do not persist. Blob-related or rollup-specific charges can require additional fields or a different fee breakdown; the basic execution multiplication should not be mislabeled as every possible cost.
Separate recorded fields from an explorer’s interpretation
Explorers organize raw records into labels, token lists and decoded contract interactions. Decoding depends on information such as the contract interface. An internal call shown in a trace is part of the execution of a transaction; it is not necessarily a separately signed transaction submitted by a user.
When the result matters, keep the network, transaction hash and relevant block context, then compare the displayed explanation with receipt fields and the identified contract. An explorer makes evidence easier to inspect, but its friendly presentation is not an independent guarantee of safety, ownership or finality.
Direct answers
Questions people ask
Does success mean I received the asset I intended?
No. It means the transaction’s execution succeeded. Check the exact contract, recipient and resulting state or events; a similarly named token can be a different asset.
Why does a token transfer show zero ETH value?
The value field records native ETH attached to the transaction. A token transfer updates balances inside a contract and can have zero native ETH value.
Is an internal transaction a second signed transaction?
Usually the label describes a call within the execution trace of one transaction. Read the explorer’s terminology and distinguish those calls from top-level signed transactions.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
A block explorer turns chain data into searchable pages for blocks, transactions, addresses and tokens. Start with the network and transaction hash, then inspect inclusion, execution status, recipient, calldata, logs and fees. Labels and decoded views add interpretation to the underlying records.
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimExecution status: Receipt success describes EVM execution, not the legitimacy of an asset or agreement
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimToken transfers: Token events and contract state differ from the transaction’s ETH value field
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimExecution fee: Gas used multiplied by the effective gas price
Scope: Ethereum. Verification: verified · 2026-10-02T15:10:23.134Z.
Link to this claimRevision history
- — First publication after primary-source research and independent automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Block explorersethereum.org contributors
Supports the fields a learner can inspect and the distinction between execution and consensus views.
Locator: Execution data; transactions; accounts; tokens; consensus layer data · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:42:49.128620+00:00Open source - JSON-RPC APIethereum.org contributors
Defines chain identity, balance/nonces, read-only simulation and receipt/status/log fields.
Locator: eth_chainId; eth_getBalance; eth_getTransactionCount; eth_call; eth_getTransactionReceipt · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:47.605538+00:00Open source - Ethereum transactionsethereum.org contributors
Supports nonce ordering, value versus calldata, signed transaction fields, receipts and transaction inclusion.
Locator: What is a transaction; the data field; transaction lifecycle · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.399251+00:00Open source - Interacting with smart contractsethereum.org contributors
Supports read-only calls, state-changing transactions, ABI decoding and limits of simulation.
Locator: Reading; writing; understanding contract ABIs; events and logs; simulating · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.398262+00:00Open source - ERC-20: Token StandardEthereum Request for Comments
Defines fungible token balances, optional display metadata and spending allowance behavior.
Locator: Methods: decimals, balanceOf, transfer, approve, transferFrom, allowance · Version / scope: 583335b7912e51b1ea515bb662532dd29b27e786 · Retrieved: 2026-10-02T14:35:55.037727+00:00Open source - Gas and feesethereum.org contributors
Supports gas units, ETH/gwei units, base/priority fees, resource limits and charges for executed failed transactions.
Locator: How are gas fees calculated; base fee; gas limit · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:40.393022+00:00Open source - Proof of stakeethereum.org contributors
Supports 12-second slots, 32-slot epochs, stake-weighted checkpoint voting and block verification.
Locator: Validators; transaction execution; finality; fork choice · Version / scope: dcc900ff125891da5b6c723b905a7113cf1bd864 · Retrieved: 2026-10-02T14:35:43.818781+00:00Open source - Geth built-in tracersGo Ethereum maintainers
Documents internal calls as nested execution frames within a transaction rather than separate signed submissions.
Locator: callTracer: call frames, nested calls and top-level execution · Retrieved: 2026-10-02T15:02:21.514441+00:00Open source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “How to read an Ethereum block explorer.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/ethereum-block-explorer/