Block headers at a glance

Headers summarize relationships and commitments rather than every underlying record.

LET’S PICTURE IT

A book’s cover and index identify the edition without printing every page on the cover.

SEE IT FOR YOURSELF

Link blocks, then see what an edit breaksStep 1 / 4

The first toy block records Maya sending Leo three units. A1 is an illustrative fingerprint label, not a real cryptographic digest.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

Follow the parent relationship

A parent reference connects a block to an earlier block. It helps identify ancestry but does not by itself establish that the entire chain is accepted or valid.

Read commitments by meaning

State, transaction and receipt roots commit to different datasets. A root’s byte length does not tell you which proof algorithm or claim applies.

Inspect resource and time context

Headers include execution context such as gas-related and timestamp information under the applicable format. Those values must satisfy protocol rules.

Use the intended schema

Upgrades can add fields and change processing requirements. A parser should target a specified network fork rather than assuming one fixed universal field list.

Map the protocol concept

header summary:
parent relationship
state commitment
transaction commitment
receipt commitment
resource and time context

A conceptual model. Exact fields, limits and processing rules must be checked against the intended network fork.

QUICK CHECK · NO PRESSURE

Are state and receipt roots interchangeable commitments?

Your progress stays in this browser.

Keep exploring the original referenceethereum.org ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.