A blockchain is a shared digital record book that many independent computers hold copies of, where new entries are grouped into blocks and each block is cryptographically linked to the one before it, forming a chain that is very hard to alter after the fact. Put simply, blockchain works by having a network agree on a single ordered history of transactions, then locking that history in place with math so that changing an old record would require redoing everything that came after it on a majority of machines at once.
Key takeaways
A blockchain is a distributed ledger copied across many computers rather than held by one company; transactions are bundled into blocks that are chained together with cryptographic hashes; a consensus mechanism lets strangers agree on which block is valid without a central referee; tampering is impractical because altering one block breaks every block after it; the design trades speed for trust, transparency, and resistance to censorship.
What problem is blockchain actually trying to solve?
For most of computing history, keeping a trustworthy shared record meant appointing someone to run it: a bank kept the ledger of your balance, and everyone had to trust that the bank recorded things honestly. That works, but it puts one party in charge and creates a single point of failure or control. The harder question is whether a group of strangers who do not trust each other can maintain one agreed-upon record without a boss in the middle.
Blockchain is one answer to that question. It lets participants share a single history that no individual can quietly rewrite, so cooperation does not depend on trusting any one operator. That is why the technology first became famous through digital money, where the record being protected is who owns which coins. You can see the original example of this idea in action on our guide to Bitcoin.
What is inside a block?
Think of a block as a page in a ledger. Each page contains a batch of transactions, a timestamp, and two special fingerprints. The first fingerprint is a hash of the block's own contents, a short string of characters generated by running the data through a one-way mathematical function. Change even a single comma in the block and that fingerprint changes completely, which makes tampering obvious.
The second fingerprint is the hash of the previous block. This is the crucial trick. Because every block carries the fingerprint of the one before it, the blocks are woven into a strict order. If someone edits an old block, its fingerprint no longer matches the reference stored in the next block, and that mismatch cascades down the entire chain. To hide the edit, an attacker would have to recompute every block from that point forward, faster than the honest network is building new ones.
How do hashes make a blockchain tamper-resistant?
A cryptographic hash function takes any input and produces a fixed-length output that looks random, cannot be reversed to reveal the input, and changes drastically with the tiniest change to the data. These properties are what turn a plain list into a tamper-evident chain. Because each block commits to the exact contents of the previous block through its hash, the history is effectively sealed once enough blocks have been stacked on top.
This is why people describe blockchain records as immutable, though a more precise word is tamper-resistant. Nothing is physically impossible; it is simply so expensive and coordinated an effort that it becomes impractical. The deeper a transaction is buried under later blocks, the more work an attacker would need to unwind it, which is why users often wait for several confirmations before treating a transfer as final.
How does the network agree on which block is next?
If thousands of computers can each propose new blocks, something has to decide whose block the whole network accepts. That mechanism is called consensus, and it is the beating heart of a blockchain. Consensus rules let a decentralized group settle on one version of history without a central authority casting the deciding vote.
Two approaches dominate. Proof of work asks participants, often called miners, to spend real computing power solving a hard numerical puzzle; the first to solve it earns the right to add the next block, and redoing that work is what makes rewriting history costly. Proof of stake instead asks participants to lock up coins as collateral; the network chooses validators based partly on that stake, and anyone caught cheating can lose it. Both aim for the same outcome, honest behavior being more profitable than dishonest behavior, but they reach it with different costs and trade-offs.
Walk me through a transaction step by step
Following a single payment from start to finish is the clearest way to see the whole system cooperate.
- You create a transaction. Using your wallet, you sign an instruction with your private key that says you are sending funds to a particular address.
- You broadcast it. Your wallet sends the signed instruction out to the network, where it waits in a pool of pending transactions.
- Nodes check it. Independent computers verify that your signature is valid and that you actually have the funds, rejecting anything that fails these tests.
- A block is assembled. A miner or validator gathers a batch of valid pending transactions, including yours, into a candidate block.
- Consensus locks it in. The network agrees on that block through its consensus rules and appends it to the chain, giving your transaction its first confirmation.
- Confirmations accumulate. As further blocks stack on top, your transaction sinks deeper into the history and becomes progressively harder to reverse.
Is every blockchain public and decentralized?
Not necessarily, and this is a common misunderstanding. Public blockchains like the ones behind major cryptocurrencies are open: anyone can read them, submit transactions, and run software that helps maintain them. Their transparency is a feature, since anyone can audit the ledger. Networks such as Ethereum fall into this category and add programmable smart contracts on top of the basic ledger.
There are also private and permissioned blockchains used by companies, where a limited set of approved participants maintain the ledger. These sacrifice openness for speed and control and are really a different tool for a different job. When people debate whether blockchain is genuinely decentralized, the honest answer is that it depends on the specific network's design, not on the word blockchain itself.
What are the real limitations of blockchain?
Blockchain is powerful but not magic, and pretending otherwise leads to disappointment. The biggest limitation is throughput: because many machines must process and store the same data, public blockchains are typically slower and handle fewer transactions per second than centralized systems. Storage grows endlessly as the chain lengthens, and energy use can be significant for proof-of-work networks.
There is also a truth problem the technology cannot solve. A blockchain guarantees that data has not been altered after it was recorded, but it cannot guarantee the data was accurate when it went in. Garbage entered honestly is still garbage, faithfully preserved. Understanding these boundaries helps you judge which problems blockchain is genuinely suited to and which are better served by an ordinary database.
