twitter

discord

website

github

Blockchains (L2)

peaq

# peaq Average Relay Chain inclusion time Methodology

## 1. Overview

This metric measures the average time it takes for Peaq parachain blocks to be included in the Polkadot relay chain, expressed in milliseconds and aggregated daily. It provides insight into the efficiency of Peaq's parachain-to-relaychain communication and the overall network performance. The calculation compares timestamps between when blocks are created on the Peaq parachain versus when they are officially included and recorded in the Polkadot relay chain.

## 2. Data sources

- **Polkadot relay chain events**: Blockchain events from the Polkadot relay chain, specifically `CandidateIncluded` events from the `paraInclusion` pallet that record when parachain blocks are included in relay chain blocks
- **Polkadot chain identifiers**: Chain ID mapping data that connects parachain identifiers to specific blockchain networks like Peaq
- **Peaq parachain blocks**: Block data from the Peaq parachain including block hashes and timestamps when blocks were created

## 3. Step-by-step calculation

### Component A: Relay chain inclusion event extraction
- **Purpose**: Identifies when Peaq parachain blocks are included in the Polkadot relay chain
- **Logic**: Filters Polkadot relay chain events for the `paraInclusion` pallet and `CandidateIncluded` method. Extracts the `paraHead` field (representing the parachain block hash) and `paraId` field (identifying which parachain) from the event data JSON structure. Joins with chain identifier lookup data to filter only for events where the `paraId` corresponds to Peaq, ensuring only Peaq-specific inclusion events are captured.
- **Key fields**: `relay_chain_timestamp`, `para_head` (block hash), `para_id` (parachain identifier), `chain_id`

### Component B: Parachain block timing correlation  
- **Purpose**: Establishes the timing relationship between parachain block creation and relay chain inclusion
- **Logic**: Joins the filtered relay chain inclusion events with Peaq parachain block data using the `para_head` field (from relay chain events) matched to `block_hash` (from parachain blocks). This creates a correlation between when blocks were created on Peaq and when they were included in the relay chain. Captures both the `parachain_timestamp` (when the block was created) and `relay_chain_timestamp` (when it was included).
- **Key fields**: `parachain_timestamp`, `relay_chain_timestamp`, `block_hash`

### Component C: Inclusion time calculation
- **Purpose**: Computes the actual time difference between block creation and relay chain inclusion
- **Logic**: Calculates the timestamp difference between `relay_chain_timestamp` and `parachain_timestamp` using milliseconds as the time unit. This represents the inclusion time - how long it took for a Peaq block to be processed and included in the Polkadot relay chain after it was created.
- **Key fields**: `relaychain_inclusion_time` (in milliseconds)

### Final aggregation
- **Time grouping**: Groups all inclusion time measurements by day using timestamp truncation to day boundaries
- **Daily averaging**: Calculates the average inclusion time across all block inclusions that occurred on each day, providing a daily average inclusion time metric
- **Metric finalization**: Applies the `finalize_metric_avg_relaychain_inclusion_time` macro with a `fill_zeros` strategy to handle days with missing data and applies chain availability filtering to ensure data quality standards
- **Final calculation**: The final metric value represents the average number of milliseconds it took for Peaq parachain blocks to be included in the Polkadot relay chain on each given day

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

avg(relay_inclusion_timestamp - parachain_block_timestamp)

Average time between parachain block production and Relay Chain inclusion.

peaqPEAQ

Average Relay Chain inclusion time

Average Relay Chain inclusion time

Competitive landscape

Chain breakdown