Tempo is a Layer 1 blockchain purpose-built for global payments, developed in partnership with leading fintechs and Fortune 500 companies and incubated by Stripe and Paradigm. It delivers high-throughput, low-cost global transactions with sub-second finality, predictable fees, and native stablecoin support.

website

twitter

Blockchains (L1)

Tempo

# Tempo Block time Methodology

## 1. Overview

Block time measures the average time it takes for a new block to be added to the Tempo blockchain. The operational speed of the network and its capacity to process transactions and update the ledger state are reflected by this metric. It is utilized as a primary indicator of network latency and consistency for the Tempo L1 blockchain.

## 2. Data sources

- **Blockchain events**: Block timestamps and block numbers from the Tempo network

## 3. Step-by-step calculation

### Component A: Block data extraction

- **Purpose**: Capture the necessary temporal and sequential metadata for the blockchain.
- **Logic**: Block timestamps and block numbers are retrieved from the network. The genesis block is filtered out of the dataset to ensure that only valid intervals between active blocks are considered for the calculation.
- **Key fields**: `timestamp` (timing), `number` (sequence)

### Component B: Interval calculation

- **Purpose**: Determine the specific time elapsed between successive blocks.
- **Logic**: The timestamp of each individual block is compared against the timestamp of the block with the immediately preceding block number. The difference between these two timestamps is calculated in milliseconds to establish the duration of each block interval.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time)

### Component C: Daily averaging and finalization

- **Purpose**: Aggregate individual intervals into a standardized daily metric.
- **Logic**: All calculated block intervals are grouped by day using UTC boundaries. The average value of these intervals is calculated for each day. Data is filtered to ensure only approved and available chain data is included in the final output, maintaining daily granularity with UTC day boundaries.
- **Key fields**: `block_time` (interval duration), `timestamp` (daily granularity)

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

avg(block_timestamp - previous_block_timestamp)

Tempo

Block time

Block time

Competitive landscape