Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Heima is a specialized identity and data verification blockchain powered by Polkadot Relay chain.

HEI holders own and govern the protocol. Heima’s investors include LD Capital, Digital Renaissance, Signum Capital, and others.

website

twitter

github

discord

etherscan

Blockchains (L2)

Heima

# Heima Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Heima blockchain, expressed in milliseconds and aggregated daily. This metric provides insight into the blockchain's performance and throughput characteristics, helping users understand the network's block production consistency and timing. The calculation computes the time difference between each block and its predecessor, then averages these intervals across all blocks produced within each calendar day.

## 2. Data sources

The block time calculation relies on the following raw data sources:

- **Heima blockchain block data**: Raw block records from the Heima L2 network containing block metadata, timestamps, and sequential block numbers
- **Block timestamps**: Precise timestamp data indicating when each block was produced and added to the blockchain
- **Block numbers**: Sequential identifiers for blocks used to establish the chronological order of block production

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieve and prepare raw block data from the Heima blockchain
- **Logic**: Extract block timestamps and block numbers from Heima blockchain data. Filter out the genesis block (block number 0) since it has an artificial timestamp at the start of Unix time that would skew calculations. Cast timestamp and block number fields to appropriate data types for further processing.
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential block identifier)

### Component B: Sequential block pairing
- **Purpose**: Create pairs of consecutive blocks to enable time interval calculations
- **Logic**: Use a lag window function ordered by block number to pair each block with the timestamp of the immediately preceding block. This creates a dataset where each row contains both the current block's timestamp and the previous block's timestamp, enabling time difference calculations.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: Compute the time difference in milliseconds between each block and its predecessor using timestamp difference functions. Truncate block timestamps to daily granularity to enable daily aggregation. Filter out any records where the previous timestamp is null (which occurs for the first block in the sequence).
- **Key fields**: `timestamp` (daily truncated timestamp), `block_time` (interval in milliseconds)

### Final aggregation
- **Combining components**: Group all block intervals by day and calculate the average block time for each calendar day
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Block times are aggregated using daily boundaries, with timestamps truncated to day level before grouping
- **Final calculation**: The final metric represents the arithmetic mean of all block time intervals within each day, measured in milliseconds, providing a daily average block production time for the Heima network

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

avg(block_timestamp - previous_block_timestamp)

HeimaHEI

Block time

Block time

Competitive landscape

Chain breakdown