Blockchain

Overview

Why Blockchain matters

Imagine several organizations needing a common history of transfers, while none wants another organization to be the sole record keeper. A normal database has an administrator who can change entries or set access rules. A public blockchain instead lets many computers independently check the protocol's rules and maintain copies of a ledger. Its value is not simply that records are distributed; it is that the network has a way to resolve disagreement about their order and validity.

How it works

A user creates and signs a transaction, such as spending previously received bitcoin. Network nodes check basic validity rules, and a block producer groups eligible transactions into a candidate block. The candidate refers to an earlier block by its hash, creating a history whose links become inconsistent if an old block is changed. Participants verify the new block and update the state they consider valid. How competing histories are resolved depends on the system: Bitcoin uses proof of work and chain selection rules; other chains may use voting, staking and explicit finality. A transaction can be broadcast but unconfirmed, included but not yet sufficiently final, or accepted by a payment business only after extra checks. None of those distinctions disappears because the word blockchain is used.

What evidence is actually on-chain?

A block usually records protocol-level data, not a complete business narrative. If a wallet sends a token, the chain might show a contract call, emitted events and a resulting token balance. An order number, customer email or shipping decision may exist only in a merchant database. This separation helps explain why reconciliation is still needed after a confirmed payment. It also matters for dispute resolution: evidence that funds moved is not identical to evidence that a customer authorized a specific purchase. Different blockchains store different data and expose different guarantees. In any payment investigation, identify the chain first, then the transaction, then the asset movement, and finally the corresponding business record. Even a perfectly intact blockchain cannot repair incorrect inputs supplied by a business or a stolen key.

A real-world payment example

A retailer receives a crypto payment for an invoice. The blockchain may prove that an amount moved to an address, but it does not know the retailer's order ID, refund policy or whether the product was delivered. Payment software must connect the verified transfer with the intended invoice and decide when to mark it paid. An explorer can help a support agent inspect the public transfer history; internal order records still complete the commercial picture.

Limits and common misunderstandings

A blockchain does not make a compromised private key safe, reverse a mistaken transfer, or guarantee useful privacy. Public chains expose transaction information, and large-scale transaction validation can be slower or more expensive than conventional databases. Also, hashes make unauthorized historical changes detectable under the chain's security assumptions; they do not make rewrites physically impossible under all circumstances.

How it differs from related concepts

A blockchain is one kind of distributed ledger, but not every distributed ledger uses chained blocks. A database record, blockchain transaction and merchant payment status describe different layers of the same activity.

Explore further

Official background: technical documentation.

Related glossary terms: Block, Consensus, Crypto Payment.