A blockchain works by grouping records into blocks, linking those blocks cryptographically, and applying agreed rules so participating computers can check and maintain the ledger. A transaction is not accepted merely because someone presses Send; it must pass the network’s checks.
If you are new to the terminology, start with the cryptocurrency, digital currency and blockchain beginner guide. This article focuses on the recordkeeping process, not token prices.
Sources checked on 7 October 2026. Examples are simplified teaching models, not descriptions of every network.
What is a blockchain ledger?
A ledger is a record of activity. In a blockchain, groups of records are linked using cryptographic identifiers. Changing earlier data changes its identifier and makes the linkage inconsistent. Network validation and consensus rules determine which history participants accept. NIST describes blockchains as tamper-evident and tamper-resistant; those terms are more precise than saying that changing history is absolutely impossible.
A useful distinction is between detecting an alteration and preventing an altered history from being accepted. Hash links help with the first. The network’s rules and security assumptions matter for the second.
How does a hash help secure blockchain technology?
A cryptographic hash helps reveal changes to recorded data and links a block to the preceding block. It provides tamper evidence; it does not secure the whole network by itself. A hash function turns an input into a fixed-length output. Recomputing it from the same input produces the same result, while changing the input produces a different result with overwhelming probability.
For example, imagine a record saying “Alex sends 2 units to Sam.” Changing the amount to 20 changes the record’s hash. A block’s identifier depends on its contents, and later blocks refer to earlier block identifiers. Other participants can recompute the hashes and detect an inconsistent chain. An attacker may recompute their own copy, so validation, consensus and the network’s security assumptions also matter.
Hashing is different from encryption: it does not hide public transaction details. It is also different from a digital signature, which helps prove authorization. NIST’s blockchain overview explains cryptographic links and tamper evidence. These distinctions are the foundation for understanding the transaction journey below.
How a blockchain transaction works: a simple journey
Consider an illustrative payment from Alex to Sam. We will follow the idea rather than pretend that all blockchains use the same account model.
- Prepare the action. Alex’s wallet builds a transaction identifying the intended destination and action. For a token transfer, contract details may be involved.
- Authorize it. A cryptographic signature provides evidence of authorization. The wallet must not reveal the private signing key to the recipient.
- Broadcast it. The signed transaction is sent to the network. Broadcast is a request for processing, not proof of settlement.
- Check it. Nodes examine whether it follows the protocol’s rules, including the relevant authorization and spending conditions.
- Include it. A block producer can include eligible transactions in a proposed block.
- Accept the history. Other participants check the block and follow the network’s consensus rules. Confirmations or finality then help express settlement confidence.
Bitcoin.org’s explanation introduces signatures and confirmations for Bitcoin. Ethereum’s transaction documentation describes its account-based transaction fields and lifecycle. Reading both is a reminder that one network’s terminology is not universal.
Wallets, nodes and block producers have different jobs
| Component | Primary role | What it does not establish |
|---|---|---|
| Wallet | Helps construct and authorize user actions. | That the recipient or smart contract is trustworthy. |
| Validating node | Checks activity against protocol rules. | That external information in a record is true. |
| Block producer | Proposes a block under the network’s mechanism. | Permission to ignore rules checked by other nodes. |
| Block explorer | Displays information about a network. | Ownership of the keys or control over the funds. |
This separation helps explain a common support problem: a wallet can display a pending transaction even though no block has included it yet. The interface, broadcast system and accepted ledger are different layers.
Proof of work vs proof of stake
Consensus is how participants coordinate around an accepted history. Bitcoin uses proof of work; Ethereum uses proof of stake. Proof of work relies on computational work in block production. Proof of stake uses validators and staked assets under protocol-specific rules. Neither phrase means that every participant votes once on every transaction. See Ethereum’s consensus overview for the distinction.
For a beginner, the important next question is: what would have to fail or be compromised for the accepted history to change? Different networks have different assumptions. A familiar brand name or an attractive block explorer cannot answer that question on its own.
Where smart contracts fit
A smart contract is code deployed to a supported blockchain that runs according to defined rules when called. It can implement token transfers or other applications. It does not independently establish that a real-world item exists or that an external promise will be fulfilled. Ethereum’s smart-contract introduction explains the code-and-state model.
Suppose a record says a shipment arrived. The ledger may preserve that submitted record, but someone or some device still had to report the arrival. Evaluate the input process as well as the ledger.
Public and permissioned blockchains
Some networks allow broad public participation; others restrict who may validate or submit records. Permission rules change the trust model. “Uses blockchain” does not necessarily mean “has no administrators,” “hides all data,” or “requires a publicly traded token.”
Ask a vendor to identify the actual participants, permissions, recovery procedures and data being shared. Those answers are more informative than a marketing label.
How to interpret a transaction status
Use this reading exercise with a public transaction record, without sharing any private key:
- Identify the network and transaction identifier.
- Check whether the record is pending, included, successful or failed.
- Distinguish the destination address from any token contract address.
- Check the recorded fee and the asset used to pay it.
- Separate ledger inclusion from a receiving service’s required confirmations.
For the fee field, see our gas-fee calculation guide. For the signing and custody layer, see hot wallets, cold wallets and recovery. The same asset label can also appear on different networks, which matters when receiving a stablecoin payment.
Frequently asked questions
Can blockchain records be changed?
The accepted history is designed to resist alteration, but security depends on the network. Reorganizations, governance and permissioned administration need to be considered rather than assuming absolute immutability.
Does a blockchain make an application private?
No. Public ledgers can expose transaction activity. Address-based records are not a promise of anonymity.
Does blockchain guarantee that stored information is correct?
No. It can preserve records while the underlying input remains inaccurate. Input validation is a separate problem.
Sources and next steps
Read NIST’s overview, Bitcoin.org and the linked Ethereum documentation for network-specific details. Return to the beginner learning hub to connect the ledger to assets, wallets and costs.
Featured image: illustrative image by Shubham Dhage on Unsplash.
