AI & Tech One-page note UK only
Blockchain Explained Simply
Blockchain is basically a shared record book that's very hard to rewrite. Here's how blocks, hashes and chains work, and why it's not just about crypto. Save this page.
Good to know
General info, not financial advice. Crypto risk info: FCA (UK). Sources: NIST, Bank of England, FCA, HM Treasury. Checked Nov 2026.
What's on the page
The note as text, so you can read it, copy it or use a screen reader.
A shared record book
- A "ledger" of transactions
- Copies kept by many computers
- Often no bank or boss in charge
Blocks and chains
- New records are bundled into blocks
- Each block holds the previous block's "hash"
- That links them into a chain
The hash
- A short digital fingerprint of data
- Change one letter: a totally new fingerprint
- So editing an old block breaks the chain
Who decides what's true?
- Computers follow set rules to agree
- Once added, records are very hard to change
- Bitcoin-style systems: secure but costly to run
Not just crypto
- Smart contracts: code that runs on the chain
- UK plans a blockchain-style government bond (DIGIT)
Watch out
- "Blockchain = safe investment": crypto can fall to zero
- "FSCS will cover me": highly unlikely for crypto
Sources
- NIST CSRC Glossary: blockchain; block (NISTIR 8202 definition); block header; hash function; consensus model; smart contract; permissioned; permissionless
- NIST IR 8202: Blockchain Technology Overview (Oct 2018), abstract
- Bank of England: What are cryptoassets (cryptocurrencies)?
- FCA InvestSmart: Crypto basics
- GOV.UK (HM Treasury): UK moves closer to launching first digitally native government bond (2 Nov 2026)
- Government Office for Science: Distributed ledger technology: Blackett review (2016)
How we checked this
Every fact on this note comes from the 6 sources listed here, checked against official or peer-reviewed sources where possible. AI tools help with drafting; a person checks every fact against the sources. How we research
Spotted a mistake? Tell us and we'll fix it and log it on the corrections page.