What Is Blockchain and How Does It Work?

A ledger is simply a record of who did what and when, like the running list of transactions in a bank account. A blockchain is a ledger with three special qualities:

• Shared: Instead of one company holding the only copy, the same ledger lives on many computers at once.
• Append-only: You can add new entries to the bottom, but you cannot edit or delete what is already there.
• Verifiable: Anyone can check the records for themselves and confirm nothing has been tampered with.

Picture a group spreadsheet that updates on everyone's screen at once, where past rows are locked for good. That is the spirit of a blockchain. Since the history cannot be quietly rewritten, people can lean on it without having to fully trust each other or a central authority.

The "block" in blockchain is just a batch of records grouped together, like one page of our notebook. The "chain" is what links those pages in order. The glue holding them together is called a hash.

A hash is a digital fingerprint for a chunk of data. You feed in any information, and a hashing program spits out a short, unique-looking code. Change even one comma in the original data and the fingerprint changes completely. That makes hashes an excellent tamper-detector.

Here is the clever part. Every block contains the hash of the block before it. So block number 5 carries the fingerprint of block 4, which carries the fingerprint of block 3, and so on back to the very first block. If someone tried to alter an old block, its fingerprint would change, breaking the link in every block that came after. The tampering would jump out at everyone right away. This chained-fingerprint design is exactly why a blockchain is so hard to fake.

A blockchain does not sit on one big server in one company's building. Copies of it are stored on many separate computers spread around the world, and each of those computers is called a node.

When someone adds a new block, the update spreads to every node, so they all keep matching copies. This is what people mean by decentralization: no single owner, no single point of control, no single point of failure. A few things this buys you:

• Resilience: If some nodes go offline, the others keep the system running.
• No gatekeeper: No single company can shut it down, censor it, or secretly alter the records.
• Open verification: Anyone can run a node and check the full history themselves.

With thousands of independent copies that all have to agree, cheating gets extremely hard. To rewrite history you would need to overpower a huge share of the entire network at once, which simply is not practical on a large blockchain.

If no one is in charge, how do thousands of strangers agree on which new block is valid? They follow a shared rulebook called a consensus mechanism. Its job is to pick who gets to add the next block and to keep everyone on the same version of history. Two methods dominate today:

• Proof of Work (PoW): Computers compete to solve a hard math puzzle. The first to solve it earns the right to add the next block. Solving takes real electricity and computing power, so cheating is expensive. Think of it as a global lottery where buying more tickets means doing more work. Bitcoin uses this method.
• Proof of Stake (PoS): Instead of burning electricity, participants lock up some of their own coins as a deposit, called a stake. The system then picks who adds the next block, partly based on how much they staked. If they cheat, they can lose their deposit. It is like posting a security bond: behave honestly or pay the price. Ethereum uses this method.

Both chase the same goal: make honest behaviour cheaper than dishonest behaviour. PoW leans on energy and hardware. PoS leans on financial risk. PoS generally uses far less electricity, while PoW has the longest track record.

A normal database, the kind that powers your bank's website or an online store, is fast, cheap, and easy to update. But it is owned and controlled by one organization, which can edit, delete, or hide records. You are trusting that company to be honest and competent. A blockchain trades away some of that speed and control for a very different set of guarantees:

• Immutability: Past records cannot be quietly changed, so the history is dependable.
• No single owner: Control is spread across many participants instead of one administrator.
• Transparency: On public blockchains, anyone can inspect the records and verify them.
• Trust-minimization: You do not have to trust a middleman; the rules and the math do the enforcing.

These strengths come with real trade-offs. Blockchains are usually slower and more expensive per transaction than a central database, since every node has to store and check the same data. They can also be harder to fix when a mistake slips through, precisely because records are not meant to change. In short: a traditional database optimizes for speed and efficiency under one trusted owner, while a blockchain optimizes for shared trust and tamper-resistance when no single owner is trusted.

Most people first meet blockchain through cryptocurrencies like Bitcoin, where it records who owns what without a bank. The same shared-ledger idea is being tried out in plenty of other areas:

• Supply chains: Tracking a product from farm or factory to store, so each step can be verified.
• Digital ownership: Proving who owns a digital item, certificate, or collectible.
• Cross-border payments: Sending value between countries without slow chains of intermediaries.
• Record-keeping: Tamper-resistant logs for things like diplomas, land titles, or audit trails.
• Smart contracts: Small programs that run automatically when conditions are met, with no middleman needed.

The common thread is situations where several parties who do not fully trust each other need to share one agreed-upon record. Still, not every problem needs a blockchain, which brings us to its limits.

Blockchain is a powerful tool, but it is not magic, and it is often the wrong tool for the job. A traditional database is usually the better pick when:

• One trusted party is in charge: If a single organization naturally owns the data, the overhead of a blockchain adds little value.
• Speed and scale matter most: Central databases can handle far more transactions per second, far more cheaply.
• Privacy is essential: Public blockchains expose data to everyone, which is unsuitable for sensitive information.
• You may need to correct mistakes: Immutability becomes a burden when errors must be fixed or data must be deleted on request.

A good rule of thumb: reach for a blockchain only when multiple parties who distrust each other must share one record that no one can secretly alter, and there is no neutral authority everyone already accepts. For everything else, a well-run ordinary database is simpler, faster, and cheaper. Once you grasp both tools and what each one costs you, the hype is a lot easier to judge calmly.