What it means
A blockchain records updates in an ordered series of blocks. A block typically includes a header with identifying metadata and a body holding transactions or other records.
Linking each new header to the previous block through a cryptographic hash makes later changes detectable under the network's rules. NIST's blockchain overview describes blocks, headers, transactions, hashes, and consensus as parts of a distributed ledger.
Different networks choose different block sizes, timing, and validation methods. A description of a Bitcoin block should not be assumed to match every private or public chain.
Before a transaction enters a block, network participants may check whether it is valid under protocol rules. Once included, it can still be affected by a short-lived competing chain or a reorganisation, depending on the system.
A manager accepting a payment should understand what the network and their service provider count as sufficiently settled. A block can hold many transactions, but capacity is finite under the network's design.
When demand exceeds the rate at which blocks can be added, fees or waiting times can rise. The number of transactions per block varies with their size and other rules, so a simple fixed capacity claim can be misleading.
The previous-block link gives a chain its tamper-evident structure, not magical immunity to error. A transaction entered under the wrong address can be faithfully recorded as the wrong payment.
If the key holder was tricked into signing it, the ledger may still show a valid signature, so operational controls remain necessary. For a finance manager, a block explorer can help trace a transaction identifier to an observed block and later confirmations, which is evidence of what the chain reports, not proof that an off-chain customer, invoice, or legal owner is correct.
Reconcile the ledger event with the business transaction and custody records. Do not confuse a blockchain block with a block of securities in trading, where the same word means a large order, so context should accompany any unqualified use of block in a report.
In practice
Real-world examples.
Example
A customer sends a digital-asset payment that appears in a newly added block. The merchant payment policy waits for further settlement under that network before releasing a high-value order. A screen showing one block is evidence of inclusion, not a universal guarantee of finality.
Example
A finance team checks a transaction identifier against a public ledger and finds it in a block. The destination address is not the address on its invoice. The transaction may be valid on the chain yet fail to settle the intended commercial debt.
Example
A network experiences a rush of transactions while its block capacity remains constrained. Users offer higher fees to get included sooner. The operations manager allows more time for settlement rather than assuming every payment will fit in the next block.
Formula
Calculation
Illustrative block fill rate = transaction data used / maximum allowed transaction-data capacity x 100, under the network's own measure. If a block uses 800 units of a 1,000-unit allowance, the fill rate is 800 / 1,000 x 100 = 80%. Some networks use weights or gas rather than simple bytes, so the unit must be specified.
A second block that uses 950 units of the same 1,000-unit allowance has a fill rate of 95%. The average fill rate across the two blocks is (80% + 95%) / 2 = 87.5%, which suggests the network is running close to capacity and that fees or waiting times may be rising.Case study
Seen in the real world.
Fictional example: Quill Export accepted a digital-asset payment for a shipment worth the equivalent of $50,000. An employee saw a transaction listed on a website and marked the invoice paid immediately. Finance manager Noor checked the transaction identifier, destination address, network, inclusion in a block, and the company settlement policy. The address was correct, but the first block had only just appeared. Noor waited for the number of confirmations required by company policy and reconciled the amount against the invoice after accounting for any network and exchange costs.
She also recorded which custody account controlled the received asset. Quill released the shipment only when the payment met its chosen threshold. The case illustrates that a block is part of a settlement trail, while a complete business decision also needs identity, amount, address, and operational controls. Afterwards Quill added a field to its invoice template for the block number and confirmation count, so every crypto receipt could be traced back to evidence later.
Watch out
Common mistakes.
- Calling a block a cryptocurrency token rather than a container for transaction data and metadata.
- Assuming inclusion in one new block is always final under every network and payment policy.
- Treating a valid on-chain transaction as proof that the payer used the correct invoice address or had proper business authority.
Questions
People also ask.
What is inside a block?
Usually a header with metadata and a body of transactions or other records, although exact fields vary by network.
Why link blocks to earlier blocks?
Cryptographic links help make past changes detectable and support an ordered ledger under consensus rules for the network.
Does a block prove a payment is settled?
It can show inclusion, but settlement judgment also depends on the network, confirmations, address, amount, and the receiving business policy.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%Related