What Is a Blockchain and How Does It Work?
Follow a delivery record across three businesses to see how blocks link, who validates entries and when a conventional database is a better fit.

Quick Answer
How the Blocks Fit Together
What Can a Delivery Record Establish?
When Would a Database Do the Job?
Who Can See the Entries?
Quick Answer
A blockchain is a shared ledger of transactions grouped into ordered blocks. Cryptographic hashes link the blocks, and network rules determine which history participants accept. The ledger helps reveal changes to recorded data. A physical event such as a delivery still needs evidence from outside the network.
The warehouse records twelve cartons leaving the dock. The buyer counts eleven. The carrier’s portal says only “delivered.” Each participant has a different account of the same shipment. Before deciding whether a blockchain would help, separate the ability to trace each statement from the ability to establish how many cartons actually arrived.
How the Blocks Fit Together
A blockchain is a shared ledger that groups transactions into blocks in an agreed order. A block carries a cryptographic hash derived from the preceding block. Change older data and the recalculated hash will differ from the one recorded by its successor. A hash helps expose an alteration. It does not encrypt the original information or decide which version of history participants should accept.
The network applies rules to proposed entries. Checks can cover the transaction format, the signer and their authority to act. Participants use the network’s consensus mechanism to agree on an accepted history. Mining is one approach used by some networks. Businesses setting up a permissioned ledger can use other arrangements for validation and ordering.
What Can a Delivery Record Establish?
| Contributor | Statement | Evidence to check outside the ledger |
|---|---|---|
| Warehouse | Twelve cartons handed to the carrier | Does the dispatch note match the physical count? |
| Carrier | Delivery accepted at the destination | Who signed for it, and which consignment reference did they use? |
| Buyer | Eleven cartons counted, one missing | Which delivery and count sheet does the discrepancy refer to? |
Suppose the warehouse types twenty-one instead of twelve. A correctly signed entry can pass the network’s rules and still contain the wrong quantity. A signature can associate an entry with a key. It cannot count the cartons. The NIST blockchain overview discusses the difficulty of connecting an external event or a sensor reading with a trustworthy digital record.
A correction can point back to the mistaken entry and record the agreed quantity. Someone investigating the shortage can see the amended value and the earlier claim. In Hyperledger Fabric’s ledger, the current state and the ordered transactions that produced it have different roles. A pilot still needs named people who can propose and authorise a correction.
When Would a Database Do the Job?
If one company controls the warehouse, online store and stock adjustments, a database with access controls, an audit log and backups may be easier to run. Two screens can disagree because a stock code was mapped incorrectly or a delivery message arrived late. Check the product and status mappings in your integration and the shipping notifications before proposing a new ledger.
There is a stronger case to examine when several independent organisations need to verify the same history and do not want any one of them to be able to rewrite it alone. Ask who can submit an event, who verifies it and what happens when the parties disagree. Agree on a small pilot that includes a disputed delivery. A demonstration containing only successful handovers will tell you little about the cost of resolving exceptions.
Who Can See the Entries?
Permission to read, propose a transaction and validate it can be granted separately. A public network and an invitation-only business network need different access arrangements. A delivery timestamp may be worth sharing even if the buyer’s name and street address are not. Try referring to a restricted document by consignment reference and list which details each party actually needs to see.
Some cryptocurrencies use blockchains. A shared dispatch ledger need not issue a marketable token. If the business already runs a blockchain project, marketing a Web3 project tackles a separate question about reaching its community. For the missing carton, keep the first exercise simple. Put all three statements side by side. Mark the disagreement that an agreed history could explain and the one that still requires a physical count.
FREQUENTLY ASKED QUESTIONS (FAQs)
It is a shared history of transactions. Entries are grouped into blocks that refer back to earlier blocks. Participants follow rules for checking which history belongs to the network.
No. Mining is associated with particular consensus mechanisms. Other networks can agree on ordering and validation in different ways, especially when participating organisations are known.
It can preserve who recorded a delivery statement under the network’s rules. It cannot observe a loading bay. A count sheet, sensor or human witness still supplies evidence about the physical event.
No. A hash is not encryption. Visibility depends on how the network and its access permissions are designed. Decide who needs the shipment reference and who may read the underlying delivery document.
A blockchain records a history. A cryptocurrency is one use of a ledger for digital assets. An organisation can participate in a permissioned business ledger without issuing a tradable coin.
An application can derive the latest recorded state from its transactions. Fabric, for example, maintains current values alongside the history that produced them. Check which participant supplied the most recent event.





