twitter

discord

website

github

Blockchains (L2)

peaq

# peaq Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Peaq blockchain, expressed in milliseconds and aggregated daily. This metric helps assess the blockchain's performance consistency and network health by tracking how efficiently new blocks are produced over time. The calculation determines the time difference between each block and its predecessor, then computes daily averages.

## 2. Data sources

The calculation relies on:
- **Peaq blockchain block data**: Raw block information from the Peaq network containing block timestamps and sequential block numbers
- **Block metadata**: Fundamental blockchain data including precise timestamps when each block was mined/validated and sequential block numbering starting from genesis

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieve basic block information from the Peaq blockchain
- **Logic**: Extract `block_timestamp` and `block_number` from raw Peaq blockchain data, filtering out the genesis block by requiring `block_number` to be greater than zero. The data is cast to appropriate types with timestamp and integer formatting.
- **Key fields**: `block_timestamp` (when the block was created) and `block_number` (sequential block identifier)

### Component B: Previous block timestamp identification
- **Purpose**: Identify the timestamp of the immediately preceding block for each block
- **Logic**: Use a window function to retrieve the previous block's timestamp for each block, ordered by block number in ascending sequence. This creates pairs of consecutive blocks needed for interval calculations.
- **Key fields**: `previous_timestamp` (timestamp of the preceding block) alongside the current `block_timestamp` and `block_number`

### Component C: Block time interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: Compute the millisecond difference between each block's timestamp and its predecessor's timestamp. Records where no previous timestamp exists are excluded. The calculation truncates timestamps to daily boundaries for subsequent aggregation.
- **Key fields**: `block_time` (time difference in milliseconds) and `timestamp` (daily truncated timestamp)

### Component D: Daily aggregation
- **Purpose**: Calculate average block times for each day
- **Logic**: Group records by daily timestamp and compute the average `block_time` across all blocks produced on each day. Additional metadata is added including chain identifier, market sector classification, business segment, and product identification for the Peaq network.
- **Key fields**: Daily `timestamp`, average `block_time`, and standardized metadata fields (`chain_id`, `market_sector_id`, `business_segment_id`, `product_id`)

### Final aggregation
- **Combining components**: The daily averages flow through a standardized finalization macro that applies consistent formatting and data quality controls
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day containing the average block time for all blocks produced that day
- **Data quality**: Forward-fill strategy is applied to handle any missing daily data points, ensuring continuity in the time series. Chain availability filters are applied to ensure data quality standards
- **Final calculation**: The final metric represents the average time in milliseconds between consecutive blocks for each day on the Peaq blockchain, standardized with consistent metadata and quality controls

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

avg(block_timestamp - previous_block_timestamp)

peaqPEAQ

Block time

Block time

Competitive landscape

Chain breakdown