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

Polimec is a decentralized community-driven funding protocol powered by Polkadot Relay chain.

PLMC holders own and govern the protocol.

website

github

twitter

discord

Blockchains (L2)

Polimec

# Polimec Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Polimec blockchain, aggregated daily. This metric indicates network performance and consensus efficiency, showing how quickly the Polimec network produces new blocks. The calculation takes consecutive block timestamps, computes the millisecond differences between them, and averages these intervals by day to provide a daily average block time metric.

## 2. Data sources

- **Polimec blockchain blocks**: Raw block data from the Polimec network containing block production timestamps and sequential block numbers
- **Block metadata**: Fundamental blockchain infrastructure data including block timestamps that record when each block was mined or produced on the network

## 3. Step-by-step calculation

### Component A: Block data preparation
- **Purpose**: Extract and prepare raw block timestamp and number data for processing
- **Logic**: Retrieves block timestamps and block numbers from Polimec blockchain data. Excludes the genesis block (block number 0) which has an anomalous timestamp at the start of Unix time that would skew calculations. Applies incremental processing logic to focus on recent data when running incremental updates.
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential block identifier)

### Component B: Consecutive block pairing
- **Purpose**: Create pairs of consecutive blocks to enable time interval calculations
- **Logic**: Uses a LAG window function ordered by block number ascending to retrieve the previous block's timestamp for each current block. This creates pairs of consecutive blocks where each row contains both the current block timestamp and the immediately preceding 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 intervals between consecutive blocks
- **Logic**: Computes the millisecond difference between each block timestamp and its previous block timestamp using timestamp difference functions. Filters out any rows where the previous timestamp is null (which occurs for the first block in the dataset). Truncates timestamps to daily boundaries to prepare for daily aggregation.
- **Key fields**: `block_time` (millisecond interval between blocks), `timestamp` (daily boundary for aggregation)

### Final aggregation
- **Combining components**: Groups all block time intervals by day and calculates the average block time for each day
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Daily boundaries created by truncating block timestamps to day level, with all block intervals within each day averaged together
- **Final calculation**: Average of all millisecond block time intervals within each day, producing a daily average block time metric. The finalize_metric_block_time macro standardizes the output format and applies a fill_zeros strategy for missing days, ensuring consistent daily time series data with metadata fields including chain identifier (polimec), market sector (blockchains_l2), and business segment (blockchain).

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

avg(block_timestamp - previous_block_timestamp)

PolimecPLMC

Archived

Block time

Block time

Competitive landscape

Chain breakdown