1. Metrics
  2. Average Relay Chain inclusion time
  1. Metrics
  2. Average Relay Chain inclusion time

Average Relay Chain inclusion time

Average Relay Chain inclusion time measures the average time between parachain block production and its inclusion on the Relay Chain. It reflects the consensus and finality latency of a multichain ecosystem, such as Polkadot.

Sources

Token Terminal

Top 10 projects by average Relay Chain inclusion time

Latest average Relay Chain inclusion time

Token Terminal watermark

Projects

Definition
Project-specific

Overview

Average Relay Chain inclusion time measures the average time between parachain block production and its inclusion on the Relay Chain. It reflects the consensus and finality latency of a multichain ecosystem, such as Polkadot.

Data sources

  • Relay Chain event logs capturing parachain block inclusion
  • Parachain block headers and production timestamps
  • Chain metadata and registry data for parachain ID mapping

Common calculation approaches

Parachain-to-Relay Chain timestamp correlation

Inclusion latency is determined by calculating the time difference between the production of a block on a parachain and its subsequent recording on the Relay Chain. This correlation is performed for networks such as Polimec, Phala, and Interlay by matching block hashes and creation timestamps from the individual parachains with corresponding metadata stored on the Relay Chain.

Relay Chain inclusion event parsing

Consensus latency data is extracted from the Relay Chain through specific event logs that signal the successful validation of a parachain block candidate. CandidateIncluded events from the paraInclusion pallet are aggregated for networks including Kilt and Robonomics Network to measure the duration required for parachain blocks to be officially included and secured by the Relay Chain's shared security model.

Note: The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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