How Does Blockchain Work? A Plain-English Explanation
A blockchain is a shared ledger thousands of computers keep in sync. See how blocks, hashes, and consensus make it tamper-evident, in plain English.

On this page
The short answer
A blockchain is a shared record of transactions that thousands of independent computers keep identical copies of. New transactions get bundled into blocks, each block is cryptographically linked to the one before it, and the network agrees on updates using math instead of trusting a manager. Changing history means redoing everything, which is why nobody bothers.
What is a blockchain ledger?
Forget crypto for a second. A ledger is just a running list of who paid whom, and when. Your bank keeps one for your account. The difference is that the bank's ledger is private, and you have to trust the bank to keep it honest.
A blockchain flips that arrangement. Thousands of computers around the world each hold a full copy of the same ledger, and anyone can check any entry back to the very first one. Bitcoin's copy has been public since January 2009, starting with its very first entry, the genesis block, mined on January 3, 2009. As of mid-2026, roughly 23,000 reachable computers, called nodes, serve it, per Coin Dance, and holding all seventeen years of history takes about 750 gigabytes of disk space, which is why ordinary volunteers can still run full copies. Here's the contrast with a normal database in one table:
| Who controls it | How records change | Who can read it | Trust model |
|---|---|---|---|---|
Traditional database | One organization | The owner can edit or delete anything | Whoever the owner allows | Take the owner's word for it |
Blockchain | No single party; thousands of independent computers | New blocks only get added; old entries stay put | Anyone, back to the first entry | Check the math yourself |
That last column is the whole point. You don't take a company's word that your transaction happened; you look it up yourself, and so can everyone else. If one copy of the ledger disagrees with the rest, the network ignores it.
This is the foundation the rest of crypto sits on. If you want the wider picture of what cryptocurrency actually is, our cryptocurrency basics guide covers it end to end.
What's actually inside a block?
Zoom in. A block is just a batch of recent transactions, plus a small header of bookkeeping data. Think of it as one page in the ledger. Bitcoin has settled a new page about every ten minutes since 2009; plenty of chains move quicker.
The header is where the clever part lives. Every block includes a hash, which is a cryptographic fingerprint of everything inside it. A hash function takes any input, a single word or a million transactions, and crunches it into a short fixed-length string. Bitcoin uses one called SHA-256.
Two properties make hashes useful here:
- The same input always produces the same fingerprint, so anyone can re-run the math and verify a block hasn't changed.
- Change even one character of the input and the fingerprint changes completely, with no resemblance to the old one.
So a block's hash acts like a tamper seal. Alter one transaction inside the block, even by a single cent, and the hash no longer matches. Every computer checking the block spots the mismatch instantly.
Plain-English version: a hash is a fingerprint for data. Same data, same fingerprint, every time. Touch the data and the fingerprint changes beyond recognition. That's the entire trick, and it's a well-tested piece of math, not magic.
Why is a blockchain so hard to tamper with?
Because each block's header also contains the hash of the previous block. That's the "chain" in blockchain, and it's what turns individual tamper seals into a tamper-evident history.
Follow the dominoes. Say someone edits a transaction in block 100. Block 100's hash changes. But block 101 recorded the old hash of block 100, so block 101 no longer matches either. Fixing block 101 changes its hash, which breaks block 102, and so on to the newest block. One small edit forces a rewrite of everything after it.
Put numbers on it and the treadmill effect gets vivid. Suppose the chain is at block 110 when you edit block 100. You now owe rewrites for blocks 100 through 110, eleven blocks of recomputed hashes, before your version even ties the honest one. But the honest network hasn't paused. By the time you finish, it's added another block, so now you're chasing block 111. And 112. On Bitcoin, that means out-producing the world's combined mining power indefinitely, not just once, and that power stood at roughly 830 exahashes per second in mid-2026: hundreds of quintillions of calculations every second, around the clock.
Confirmations are this arithmetic viewed from the recipient's side. A payment buried six blocks deep needs an attacker to redo six blocks plus keep pace with new ones. Reversing one block is merely hard. Reversing six means winning that race six times over while the whole network pushes the other way, and the odds collapse fast.
Meanwhile, thousands of other computers still hold the original, unbroken chain. Your rewritten version disagrees with all of them, and the network's rule is simple: the copy that matches the majority wins. To make an edit stick, you'd need to out-rewrite the combined effort of the entire network, faster than it adds new blocks.
That's why people call blockchains tamper-evident rather than unhackable. Nothing physically stops you from editing your own copy. The system just makes any edit obvious, expensive, and pointless.
How does the network agree without a boss?
Nobody is in charge. So who decides which block gets added next? Two people could broadcast conflicting versions. Somebody has to break the tie, and it can't be a somebody, or we're back to trusting a middleman.
The answer is a consensus mechanism, a set of rules that lets strangers agree on one shared history. The two big approaches work roughly like this:
- Proof of work: computers compete to solve a costly math puzzle, and the winner proposes the next block. Cheating means outspending everyone else on electricity and hardware, which doesn't pay.
- Proof of stake: participants lock up their own coins as collateral for the right to propose blocks. Approve fraudulent history and the network destroys your stake.
Both designs reach the same goal from different angles: make telling the truth the only move that pays and cheating a money-loser. The trade-offs between them, energy use, speed, and security assumptions, deserve their own article, and we've written one: proof of work vs proof of stake.
A transaction's journey, start to finish
Theory is nice. It clicks faster when you follow one payment through the pipeline. Say you send a friend some bitcoin. Five things happen:
- Sign: your wallet creates the transaction and signs it with your private key, a secret that proves the coins are yours without revealing itself.
- Broadcast: the signed transaction goes out to the network, hopping from computer to computer in seconds.
- Wait in the mempool: it lands in the mempool, the shared waiting room of transactions that haven't made it into a block yet.
- Get picked for a block: block builders select transactions from the mempool, usually highest fee first, and pack them into the next block.
- Confirm: once the block is added, your transaction has one confirmation. Every block built on top adds another, burying it deeper in settled history.
Each confirmation makes reversal exponentially harder, which is why recipients wait for a few before treating a payment as final. Many services treat six confirmations as the traditional benchmark for large bitcoin payments, while smaller amounts often clear with fewer.
Worth knowing: fees and wait times aren't fixed. When the mempool is crowded, fees rise and low-fee transactions sit in the queue. Our guide to transaction fees and confirmations explains how to read the traffic and pay accordingly.
What blockchains are not good for
Honest limits matter more than hype. Let's name them. A blockchain is a brilliant tool for one job: keeping a shared record honest between strangers. It's a clunky tool for plenty of others.
- Speed and volume: matching a global card network's throughput is still a real challenge. Public chains trade raw speed for decentralization, and busy periods mean delays and higher fees.
- Privacy: public ledgers are public. Anyone can trace activity between addresses, which is the opposite of what many people assume about crypto.
- Fixing mistakes: irreversibility works against you too. Send coins to a mistyped address and no customer-support line can claw them back.
- Garbage in, garbage out: a blockchain proves its own records haven't been altered. It can't prove a claim was true when it was written. Fraud recorded on-chain is just very well-preserved fraud.
- Anything a database does better: if one trusted party can run the system, a normal database is faster, cheaper, and easier. Most things labeled "blockchain-powered" fall in this bucket.
In our experience, the privacy point is the one that surprises beginners most: people assume crypto is anonymous, then discover that every transfer they've ever made is publicly traceable.
None of this makes the technology less interesting. It just means the right question isn't "is blockchain good?" but "does this job actually need strangers to agree without a middleman?" When the answer is yes, nothing else does it better. When it's no, you're paying decentralization's costs for nothing.
Keep it in perspective: understanding how a blockchain works is not a reason to buy anything. Crypto prices are volatile, transactions are irreversible, and this article is education, not financial advice. If you use crypto for gambling, the same rule applies as always: never wager money you can't afford to lose. 18+/21+ depending on your jurisdiction.
Sources
- Bitcoin.org — FAQ — retrieved July 2026
- Bitcoin.org — How Bitcoin Works — retrieved July 2026
- Bitcoin Wiki — Genesis block — retrieved July 2026
- Coin Dance — Bitcoin Nodes Summary — retrieved July 2026
- Blockchain.com — Blockchain Size chart — retrieved July 2026
- Blockchain.com — Total Hash Rate chart — retrieved July 2026
Frequently asked questions
Can someone hack or change a blockchain?
A blockchain is tamper-evident rather than unhackable. Anyone can edit their own copy, but changing one transaction alters that block's hash and breaks every block after it, forcing a rewrite of the entire chain. Meanwhile thousands of other computers still hold the original, and the network follows whichever copy matches the majority. Making an edit stick would mean out-rewriting the whole network faster than it adds new blocks.
How many confirmations should I wait for on a Bitcoin payment?
Each block built on top of the one containing your transaction adds a confirmation, and every confirmation makes reversal exponentially harder for an attacker. Many services treat six confirmations as the traditional benchmark for large Bitcoin payments, while smaller amounts often clear with fewer. Reversing a payment buried six blocks deep means redoing six blocks while keeping pace with the whole network.
What is a hash and why do blockchains use it?
A hash is a cryptographic fingerprint of data: the same input always produces the same short, fixed-length string, and changing even one character produces a completely different one. Bitcoin uses a hash function called SHA-256. Because any alteration to a block's contents changes its hash, the hash acts as a tamper seal that lets every computer on the network instantly spot a modified transaction.
Are blockchain transactions anonymous?
No. Public blockchains are public ledgers, and anyone can trace activity between addresses, which is the opposite of what many people assume about crypto. Anyone can download the full ledger, read it, and check any entry back to the very first one; Bitcoin's record is visible all the way back to 2009. That openness is what removes the need to trust a single institution.
Can I get my crypto back if I send it to the wrong address?
No. Irreversibility is built into how blockchains work, and it cuts both ways: the same property that stops anyone from rewriting history also means no customer-support line can claw back coins sent to a mistyped address. That is why recipients wait for confirmations and why it pays to double-check an address before sending any payment.
Why do crypto transaction fees and wait times change?
Fees and wait times are not fixed. Pending transactions sit in the mempool, a shared waiting room, and block builders usually pick the highest-fee transactions first. When the mempool is crowded, fees rise and low-fee transactions sit in the queue. Busy periods on public chains bring delays and higher costs, because these networks trade raw speed for decentralization.
Go deeper with a course
About the author
Provably Fair & Payments Writer
Devon covers the technical side of crypto: how blockchains reach consensus, provably fair verification, seeds and hashes, and how deposits and withdrawals actually move — from casino approval to network confirmations.


