What it means
A blockchain batches activity into blocks rather than creating a new block for every transaction. The interval between two observed blocks is found by comparing their accepted timestamps or observation times under the chosen method.
One interval can differ from the network's stated target or typical interval. In proof-of-work systems, finding a valid block is uncertain.
Protocol difficulty may be adjusted to aim for a long-run pace, but that does not schedule the next block for an exact minute. A business promise to ship a product after exactly one target interval would therefore carry avoidable timing risk.
Ethereum uses proof of stake and divides time into twelve-second slots in its proof-of-stake design. A validator is selected to propose a block in a slot, but a slot may be empty.
Ethereum's own documentation says the time between actual blocks can therefore exceed one slot even though slot length remains twelve seconds. Block time is not block height.
Height counts accepted blocks in an observed chain, while block time measures separation in time. Dividing a height difference by a published target interval gives only a planning estimate, not a timestamp for an invoice or a guarantee of when a transfer can be used.
For a payment, a manager also needs to understand confirmation or finality rules. A transaction might wait before it is placed in a block; after inclusion, a business may require further blocks or protocol finality.
Total customer wait includes broadcast, inclusion, network confirmation, custody processing, and internal reconciliation, not just block time. Compare measured intervals only within a defined network, time window, and data source, because a missed slot, chain reorganisation, delayed observer, or difference between block timestamp and reception time can shift results.
Reporting a single interval as a permanent network speed is misleading. A finance team can put a realistic range in its operating procedure that states the specific network, measured period, confirmation threshold, escalation point, and fallback for delayed payments, while avoiding a universal block time for all cryptocurrencies or treating a published average as a service-level promise.
In practice
Real-world examples.
Example
Three consecutive blocks are observed at 10:00:00, 10:00:12, and 10:00:36. The intervals are 12 and 24 seconds, so their two-interval average is 18 seconds. That does not change a protocol's slot duration.
Example
A shop receives a payment broadcast just after a block closes. The next block arrives later than the network's long-run average. Staff wait for transaction inclusion and the shop's settlement threshold instead of releasing goods at the average time.
Example
An analyst compares two networks and sees a shorter reported average block interval on one. She also checks blocks' capacity, finality rules, fees, and the time between a customer's payment request and credited receipt before recommending it.
Formula
Calculation
Average observed block time over consecutive blocks = sum of measured intervals divided by number of intervals. If timestamps are 10:00:00, 10:00:12, and 10:00:36, the intervals are 12 and 24 seconds and the average is (12 + 24) / 2 = 18 seconds. Specify the network and timestamp method.Case study
Seen in the real world.
Fictional example: Harbor Prints accepted digital-asset payments for custom equipment. Sales had advertised that a network with twelve-second slots would always settle a payment in twelve seconds. Operations found that a block could be missed and that its internal policy required more than mere inclusion. Controller Nia rewrote the checkout notice to describe an estimated range and a confirmation rule, without promising a fixed delivery minute.
She tracked the time from customer broadcast to block inclusion and from inclusion to the threshold separately. When a slot had no block, the team did not count it as a successful confirmation. One order took longer than expected, so the service desk held shipment and told the customer the payment was still being checked. The team logged block height, transaction identifier, timestamps, and final receipt rather than treating the published slot duration as a payment guarantee.
Watch out
Common mistakes.
- Treating a target or average block interval as a guaranteed wait for the next block.
- Confusing Ethereum slots, actual blocks, height, and finality as if they all advanced together.
- Using block time alone to promise payment settlement without checking inclusion, confirmation policy, and internal processing.
Questions
People also ask.
Is block time the same as a block timestamp?
No. Block time is an interval between blocks; a timestamp is a time value recorded or observed for one block under the network's rules.
Does a twelve-second slot mean a block always appears after twelve seconds?
No. Ethereum allocates twelve-second slots, but a slot may have no block. Actual intervals between accepted blocks can be longer.
Will faster blocks always make payments final sooner?
Not necessarily. Inclusion demand, fees, chain rules, confirmation or finality thresholds, and service processing also affect the total wait.
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%