Almost every crypto headline eventually mentions “the blockchain”, usually without explaining what one is. Strip away the jargon and a blockchain is simply a shared record of transactions that no single person or company controls. Instead of one bank keeping the master ledger, thousands of independent computers each keep an identical copy and constantly check one another’s work.
This guide walks through what that means in plain English — what a block holds, how blocks link together, who keeps the records, and what the design is genuinely good and bad at.
The problem a blockchain solves
Imagine sending money online without a bank in the middle. The hard part is not moving the message — it is stopping the same coin from being spent twice. Traditional systems solve this with a trusted middleman: your bank holds the official balance and updates it. You trust them to be honest and online.
A blockchain removes the middleman by making the record public and shared. Everyone can see every balance and every transfer, and the network agrees on the order of events. There is no central database to hack, bribe, or switch off — because there is no single copy. This shared, append-only record is a type of distributed ledger.
What a “block” actually contains
Transactions are not written one at a time. They are gathered into batches called blocks. A typical block holds three things:
- A list of transactions — who sent what to whom, since the last block.
- A timestamp and other metadata — including a reference to the block before it.
- A fingerprint of the previous block, called a hash.
That last item is the clever part. A hash is a short string of characters produced by running data through a one-way mathematical function. Change a single comma in the input and the hash changes completely, but you can never run the function backwards to recover the original data.
How blocks chain together
Each new block includes the hash of the block before it. That creates a chain: block 102 points back to block 101, which points back to block 100, all the way to the very first block (the genesis block).
Because every block carries the fingerprint of its predecessor, the chain is tamper-evident. If a bad actor tried to rewrite an old transaction, that block’s hash would change — which would break the reference in the next block, and the next, and so on. To get away with it they would have to silently recompute every single block that followed, faster than the rest of the network is building new ones. On a large chain that is wildly impractical, which is why old records are treated as effectively permanent, or immutable.
Who keeps the ledger?
The copies of the chain live on computers called nodes. Anyone can run one. Each node stores the full history and independently verifies new blocks against the network’s rules — checking signatures, making sure no coin is spent twice, and confirming the maths adds up.
This is what people mean by decentralization: there is no head office. If one node lies or goes offline, thousands of others carry on. A change to the rules only sticks if a large majority of participants voluntarily adopt it.
How thousands of strangers agree
If nobody is in charge, how does the network agree on which block comes next? Through a consensus mechanism — a set of rules that makes honest behaviour the most profitable strategy. The two best-known are proof of work (used by Bitcoin) and proof of stake (used by Ethereum). Both make it expensive to cheat and rewarding to follow the rules. We compare them in detail in our guide on Proof of Work vs Proof of Stake.
What blockchains are good — and bad — at
Blockchains are excellent when you need a record that many parties can trust without trusting each other: transparent ownership, censorship-resistant payments, and rules that run exactly as written. They are deliberately slow and redundant, though, and that has costs.
| Strengths | Trade-offs |
|---|---|
| No central point of failure or control | Slower and more expensive than a private database |
| Transparent, auditable history | Everything is public by default |
| Records are extremely hard to alter | Mistakes and theft are also hard to reverse |
| Open to anyone, anywhere | You are fully responsible for your own keys |
That final trade-off — self-responsibility — is the one newcomers underestimate most. Because no company holds your account, losing access to your wallet usually means losing your funds for good. We cover how to manage that safely in Crypto Wallets and Self-Custody.
The bottom line
A blockchain is a shared, tamper-evident record kept in sync by many independent computers rather than one trusted authority. Blocks batch transactions; hashes chain them together; nodes store and verify them; and consensus rules keep everyone honest. Understand those four ideas and the rest of crypto becomes far easier to follow.
Why hashes make tampering obvious
It is worth dwelling on the hash, because it is the mechanism that makes the whole structure trustworthy. A hash function takes any amount of data and produces a fixed-length fingerprint. The same input always yields the same fingerprint, but even a tiny change to the input — a single digit, a flipped letter — produces a completely different output, and there is no practical way to work backwards from a hash to the data that produced it. Because each block stores the hash of the one before it, the blocks are cryptographically linked. Altering an old record changes its hash, which no longer matches the reference stored in the next block, and the mismatch cascades forward for anyone to see.
Distributed ledgers and the role of nodes
A blockchain is one kind of distributed ledger: a record that is replicated across many independent computers rather than held in a single master database. Each of those computers, called a node, keeps a full copy of the history and checks every new block against the network’s rules before accepting it. Nodes verify that signatures are valid, that no coin is spent twice, and that the new block builds correctly on the existing chain. Because the ledger is duplicated everywhere, there is no single copy to attack, corrupt, or quietly edit. If one node fails or tries to cheat, the others simply carry on with the version they all agree on.
Proof of work and proof of stake, briefly
Consensus is the process by which independent nodes agree on the next block without a central authority. The two best-known approaches take different routes to the same goal of making honesty cheaper than cheating. Proof of work asks participants to expend real computing power to earn the right to add a block, so rewriting history would mean redoing an enormous amount of work. Proof of stake instead asks participants to lock up value as collateral, which can be lost if they act dishonestly. Both raise the cost of attacking the network above any plausible reward. They differ mainly in their energy use, hardware requirements, and the way they distribute influence.
Public, private and permissioned chains
Not all blockchains are open to the world. A public chain lets anyone read the ledger, submit transactions, and help validate blocks; this is the model most people picture, and it maximizes openness and censorship resistance. A private or permissioned chain restricts who may join, who can write, and sometimes who can even read. Businesses and consortia often prefer this when they want the tamper-evidence and shared record-keeping of a blockchain but need to control participation for legal, privacy, or performance reasons. The trade-off is plain: permissioned systems are faster and more controllable, but they reintroduce a degree of trust in whoever manages access.
Why immutability matters
Immutability — the practical impossibility of quietly altering settled records — is the property that gives a blockchain its value as a source of truth. When a record cannot be changed after the fact, parties who do not fully trust each other can still rely on a shared history without an intermediary to police it. That underpins use cases from transparent ownership to auditable supply chains. The same property cuts both ways, though. If records cannot be reversed, then mistakes, fraudulent-but-valid transactions, and theft are equally permanent. The system enforces the rules exactly as written, with no manager to appeal to, which is both its great strength and a serious responsibility for users.
Uses beyond cryptocurrency
Although payments were the first application, the underlying idea — a shared, tamper-evident record many parties can trust — has been explored well beyond money. Supply-chain tracking can record the journey of goods so each step is verifiable. Digital identity projects aim to let people prove credentials without handing over more data than necessary. Tokenization represents ownership of assets, from documents to financial instruments, as entries on a ledger. Smart contracts let agreements execute automatically when conditions are met. Not every experiment succeeds, and a blockchain is not always the right tool, but the common thread is recording shared state in a way no single party can secretly rewrite.
Limitations and common misconceptions
Blockchains are deliberately slow and redundant, because every node independently stores and verifies the same data; that makes them poor substitutes for an ordinary database when one trusted operator would do. A few myths are worth dispelling. “Anonymous” is usually wrong — most public chains are transparent and pseudonymous, with every transaction visible. “Unhackable” overstates the case: the core ledger is extremely hard to alter, but exchanges, wallets, and applications built around it can still be compromised. And a blockchain cannot verify that real-world information fed into it is true; it faithfully records whatever it is given, accurate or not. Knowing what the technology does not do is as useful as knowing what it does.
How to think about blockchain
Stripped of the hype, a blockchain is a clever answer to a narrow question: how can many parties who do not trust each other share one honest record without a central authority? Blocks batch the entries, hashes link them so tampering is obvious, nodes store and check every copy, and consensus rules keep the majority honest. When trust is already easy — a single company managing its own data — a plain database is simpler and faster. When trust is the hard part, the blockchain’s slowness buys something valuable: a record no one can quietly rewrite. Keep that trade-off in mind and most claims about the technology become easy to evaluate on their merits.
Frequently asked questions
Is a blockchain the same as Bitcoin?
No. Bitcoin is one cryptocurrency that runs on its own blockchain. A blockchain is the underlying record-keeping technology; thousands of different projects use their own blockchains.
Can data on a blockchain be changed or deleted?
In practice, no. Once a transaction is buried under later blocks, altering it would mean re-computing every block after it and out-pacing the entire network u2014 which is economically impractical on a large chain. This is why blockchains are described as immutable.
Is everything on a public blockchain visible?
Yes. On public chains like Bitcoin and Ethereum, every transaction is viewable by anyone. Addresses are pseudonymous rather than anonymous u2014 they are not tied to your name on-chain, but the flow of funds is fully public.