A blockchain is a shared ledger whose history is stored and checked by multiple computers. Transactions are signed, broadcast, verified and grouped into blocks under common rules. It does not make every user anonymous or every application safe.
Application, protocol and network are different.
Sign, broadcast, verify, include and confirm.
Always identify the actual blockchain being used.
What a blockchain actually contains
The ledger holds ordered data, often transactions, linked so retrospective changes can be detected. Each node applies protocol rules before accepting a new state.
- Ledger: shared history
- Node: computer enforcing rules
- Consensus: agreement on valid state
The journey of a transaction
A wallet prepares the asset, network, recipient, amount and fee. A signature proves authorization without revealing the private key. The network checks the transaction before inclusion and later confirmations.
- Prepare and review
- Sign locally
- Broadcast to nodes
- Validate rules
- Include and confirm
Public does not mean anonymous
On many public blockchains, addresses, amounts and timestamps remain visible. Addresses are pseudonymous and may be linked to an identity through a service, reuse or flow analysis.
What blockchain does not guarantee
Consensus can confirm protocol compliance without proving that a website, token, smart contract or recipient is trustworthy. Separate protocol, application and transaction risk.
- No value guarantee
- No automatic reversal
- No universal legal validation
Read a transaction as limited evidence
An explorer shows that an operation was included on the network inspected; it does not prove the recipient’s civil identity or the legal meaning of the exchange.
- Check network, address, amount, status and confirmations.
- Keep the invoice or offchain agreement when needed.
Practical case: decision and limits
A wallet says “sent” but the recipient sees nothing. Start with the hash and network: the transaction may only be broadcast, included in a block or sufficiently confirmed. An internal exchange balance does not prove an onchain transfer. Keep the hash and check status before sending again; a second operation can create a duplicate payment.
A concrete verification
Compare the latest block with another source: a lagging node shows incomplete history.
Three things not to confuse
| Element | Role | Question |
|---|---|---|
| Blockchain | Stores and validates shared state | Which chain and rules? |
| Wallet | Manages keys and signatures | Who controls the key? |
| Platform | Provides an interface or service | Who is the entity and what does it hold? |
Frequently asked questions
Can a blockchain be changed?
Rules, software and recent history can change by network. Altering old validated history generally becomes very difficult.
Why are there several blockchains?
They make different trade-offs between security, capacity, cost, governance and compatibility.
Is one confirmation enough?
It depends on the network and risk. Check what the receiving service requires.
Verifiable sources
Independent educational content reviewed against primary documentation. No personalized recommendation or promise of returns. Updated October 6, 2026
