What the hell is blockchain, really? — Lesson overview
Page 1 of 7 — Section 1 of 7
- Problem setup:How to agree on “who owns what” without a central admin.
- Notebook analogy:Hashes as fingerprints; changing one page breaks the chain.
- What’s inside a block:Parent hash, tx list, tx/merkle root, miner/validator.
- Consensus and confirmations:Why blocks stack and what a fork/reorg means.
- Hands-on explorer tour:(Sepolia Etherscan) to trace 3 blocks and 1 transaction.
- Self-check with answers plus:A one-page explainer project.
Plain-English storyThink of a blockchain as a public receipt book on the internet. Everyone can read it and many people keep their own copy. New pages get added over time, and the whole book stays in sync because copies are compared constantly.
Each page (block) lists recent transactions plus a short fingerprint (hash) of the page before it. If you try to edit an older page—like changing a payment amount—the fingerprint for that page changes. That change ripples forward and breaks every later fingerprint.
Because lots of people hold copies, the honest majority will notice the broken fingerprints and reject the tampered version. To pull off a silent edit, an attacker would have to outpace everyone else and redo many pages at once, which is deliberately expensive.
Problem it solvesIt lets strangers agree on “who owns what” without a help desk or central database that can quietly change the record.
Instead of trusting one company to keep the ledger honest, many independent computers check each new page against the rules. If a page doesn’t fit (bad fingerprint, invalid transactions), it gets rejected.
This spreads trust out: no single admin can silently rewrite history, and anyone can verify balances and transactions by checking the shared record.
Your goalExplain in one minute why edits are loud and expensive, and show a friend how to verify any transaction on a public block explorer.