website

twitter

github

Blockchains (L2)

Invarch

# Invarch Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the InArch blockchain, aggregated daily. This metric helps assess network performance, consensus efficiency, and blockchain throughput. The calculation determines how long it takes on average for the InArch network to mine or validate each new block, providing insights into network health and operational consistency.

## 2. Data sources

The calculation relies on:
- **InArch blockchain block data**: Raw block records from InArch blockchain nodes containing block timestamps and sequential block numbers
- **Blockchain node records**: Direct blockchain data including precise block creation timestamps and block heights from the InArch network

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieve fundamental block information from the InArch blockchain
- **Logic**: Extract block timestamps and block numbers from InArch blockchain records. Filter out the genesis block (block number 0) since it carries a Unix epoch timestamp that would skew calculations. Apply incremental processing logic to focus on recent blocks when updating existing data
- **Key fields**: `block_timestamp` (when each block was created), `block_number` (sequential block height)

### Component B: Sequential block pairing
- **Purpose**: Pair each block with its immediate predecessor to enable time interval calculations
- **Logic**: Use window functions to associate each block with the timestamp of the previous block in the sequence. Order blocks by their block number to ensure correct chronological pairing. This creates a dataset where each row contains both the current block timestamp and the previous block timestamp
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Calculate the actual time elapsed between consecutive blocks
- **Logic**: Compute the millisecond difference between each block timestamp and its predecessor timestamp. Filter out any rows where the previous timestamp is null (typically the first block in the sequence). Truncate timestamps to daily boundaries to prepare for daily aggregation
- **Key fields**: `block_time` (milliseconds between blocks), `timestamp` (daily boundary)

### Final aggregation
- **Combining components**: Group all block time intervals by day and calculate the average block time for each date
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Daily aggregation boundaries using timestamp truncation to day level
- **Final calculation**: Average block time in milliseconds per day, standardized with InArch chain identification, market sector classification as 'blockchains_l2', and business segment as 'blockchain'. The metric represents the mean time interval between consecutive blocks for each calendar day on the InArch network

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

avg(block_timestamp - previous_block_timestamp)

Invarch

Archived

Block time

Block time

Competitive landscape

Chain breakdown