A block header is the compact set of protocol-defined fields that identifies a block and links it to important information about the chain. It is not the same as the full collection of transactions, and its exact fields differ between Bitcoin, Ethereum and other blockchain designs.
Alicia keeps a fictional school science-kit record. Tricia stores every borrowing entry, while Kai Kai makes a small cover card showing which volume it belongs to and how it connects to the preceding volume. The cover card helps identify the volume, but it cannot tell you everything inside the book.
This chapter is written for parents, children and adults who want a clear explanation of the technology without cryptocurrency speculation. The school example is fictional; no live blockchain account or student data is needed.
The quick answer
A block header is the compact set of protocol-defined fields that identifies a block and links it to important information about the chain. It is not the same as the full collection of transactions, and its exact fields differ between Bitcoin, Ethereum and other blockchain designs.
The story behind the mechanism
Alicia keeps a fictional school science-kit record. Tricia stores every borrowing entry, while Kai Kai makes a small cover card showing which volume it belongs to and how it connects to the preceding volume. The cover card helps identify the volume, but it cannot tell you everything inside the book.
1. What belongs in a header?
Bitcoin block headers include a version, previous-block hash, Merkle root, timestamp, difficulty target encoding and nonce. Ethereum has its own execution-block header fields and a different consensus architecture. A general explanation should not pretend all headers share one template.
2. A link to the previous block
A previous-block reference connects a candidate block to an earlier block. A reader can check the relationship under the network’s hashing and validation rules. Linking blocks helps make changes to history detectable, but hashing alone does not create independent consensus.
3. The Merkle root and transaction evidence
Bitcoin’s Merkle root commits to the block’s transactions. An appropriate Merkle proof can establish that a transaction is included under that root. The verifier still needs a trustworthy basis for accepting the header and the chain it belongs to.
4. Why a header is not the whole block
A header does not itself supply every transaction or every detail needed for independent verification. A lightweight client may use headers and proofs for narrower checks, while full validation requires more under the relevant protocol.
5. What a timestamp can and cannot tell us
A header’s time-related field follows network-specific rules. It is not necessarily an exact timestamp for the original real-world event. A school race result may have been measured and reported at different times.
6. Block identification is not physical truth
A cryptographically consistent header can identify an accepted digital record without proving that a delivery occurred, a student earned a mark or a source document was accurate.
7. Paper activity: book covers and pages
Write three small volumes of imaginary bookings. Give each volume a cover card pointing to the preceding volume and a summary of its entries. Hide one volume’s pages. Ask what the covers still show and what they cannot reconstruct.
8. The practical verification question
Which network defines the header, which accepted reference is being checked, what proof is supplied and what external claim remains outside the blockchain? Those questions prevent a narrow technical proof from becoming an unsupported promise.
A five-question learning check
Ask: What does this mechanism actually establish? Which network or reference does it use? Who supplies the information? What happens if a component fails? What real-world fact remains to be checked? Encourage specific answers rather than the general label ‘verified’.
A parent-and-child exercise
Use the paper example above and change one assumption: disconnect a computer, introduce a conflicting record or change a rule. Ask whether the original result is still supported. The paper activity illustrates reasoning, not real cryptographic security.
When an ordinary system may be better
A school with one accountable administrator may need only a database, signed documents and an audit trail. Blockchain is justified when its particular shared verification or governance properties solve a real problem that simpler alternatives do not adequately address.
Frequently asked questions
Does this prove every claim in the record is true?
No. Technical validity and the accuracy of outside-world claims are different questions.
Can children learn without cryptocurrency?
Yes. Fictional records and paper exercises are enough. There is no need for wallets, private keys or financial transactions.
Does every blockchain work the same way?
No. Network-specific consensus, state, data and software rules matter. Check the appropriate technical documentation for precise claims.
Continue through the learning hubs
For deeper detail, use the specialist technical companion, the English Master Blockchain guide, the Simplified Chinese guide and the main Master Blockchain hub.
Sources and scope
Technical source: https://developer.bitcoin.org/reference/block_chain.html. Broader foundation: NIST IR 8202. The school scenarios are fictional and do not describe an actual eduKateSG blockchain deployment.
Takeaway: A block header is the compact set of protocol-defined fields that identifies a block and links it to important information about the chain. It is not the same as the full collection of transactions, and its exact fields differ between Bitcoin, Ethereum and other blockchain designs.