Build once, connect everywhere. Hyperbridge gives developers the secure infrastructure to scale applications across any network.

website

twitter

github

discord

Bridges

Hyperbridge

# Hyperbridge Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Hyperbridge blockchain, aggregated daily. This metric indicates blockchain performance and network health by showing how quickly blocks are being produced. The calculation measures time differences between consecutive block timestamps and averages them by day to provide a daily block time metric in milliseconds.

## 2. Data sources

The metric uses the following raw data sources:
- **Hyperbridge blockchain block headers**: Contains block timestamps, block numbers, and validator/author information for each block produced on the Hyperbridge network
- **Block metadata**: Includes precise timestamp data for when each block was mined/validated, essential for calculating time intervals between blocks

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extracts basic block information from Hyperbridge blockchain
- **Logic**: Retrieves block timestamps, block numbers, and author information from raw Hyperbridge block data. Applies safe casting to ensure proper data types for timestamp (timestamp), block number (integer), and author ID (string). Excludes the genesis block (block number 0) which has an artificial timestamp at Unix epoch that would skew calculations
- **Key fields**: `block_timestamp`, `block_number`, `author_id`

### Component B: Time interval calculation
- **Purpose**: Calculates the time difference between consecutive blocks
- **Logic**: Orders blocks by block number and uses a lag window function to get the previous block's timestamp for each current block. Calculates the time difference in milliseconds between each block and its predecessor using timestamp difference functions. Blocks without a previous timestamp (the first block after genesis) are excluded from calculations
- **Key fields**: `block_timestamp`, `previous_timestamp`, `block_time` (in milliseconds)

### Component C: Daily aggregation
- **Purpose**: Groups block times by day and calculates daily averages
- **Logic**: Truncates block timestamps to day level granularity to group blocks by calendar day. Groups all block time intervals within each day and calculates the average block time for that day. Assigns chain identifier as 'hyperbridge' and product identifier as 'Hyperbridge Substrate' for standardization
- **Key fields**: `timestamp` (day level), `timestamp_grain`, `chain_id`, `product_id`, `block_time` (average)

### Final aggregation
- **Combining components**: The daily block time averages flow through a finalization macro that standardizes the metric format and applies chain availability filtering
- **Currency conversion**: Not applicable for block time metrics
- **Time aggregation**: Block times are calculated at the individual block level, then averaged by calendar day boundaries using day-truncated timestamps
- **Final calculation**: The final metric represents the average time in milliseconds between consecutive blocks for each day on the Hyperbridge blockchain, providing a daily measure of block production speed and network performance

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

avg(block_timestamp - previous_block_timestamp)

HyperbridgeBRIDGE

Archived

Block time

Block time

Competitive landscape

Chain breakdown