Validators process transactions and receive transactions fees (supply-side fees).

Injective is a smart contract platform for decentralized finance applications (a blockchain) and an orderbook exchange protocol. Injective was founded by Eric Chen, Albert Chon etc. and launched in 2020. Note that this dashboard only tracks Injective's blockchain business.

INJ holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue) via Burn Auctions. Injective's investors include Binance, Jump Crypto, Mark Cuban, etc.

github

twitter

discord

website

Blockchains (L1)

Injective

# Injective Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Injective blockchain, expressed in milliseconds. This metric indicates blockchain performance and network efficiency by tracking how consistently blocks are produced. The calculation processes sequential block timestamps to compute daily average block production times.

## 2. Data sources

- **Injective Cosmos blockchain data**: Raw block records containing timestamps and block heights from the Injective blockchain infrastructure
- **Block headers**: Sequential blockchain block records with creation timestamps and block height numbers
- **Blockchain infrastructure data**: Core blockchain metadata tracking block production timing and sequencing

## 3. Step-by-step calculation

### Component A: Block timestamp extraction
- **Purpose**: Retrieves raw block timing data from Injective Cosmos blockchain
- **Logic**: Extracts `block_timestamp` and `block_number` from Injective blockchain block records. Filters out the genesis block by requiring `block_number` greater than 0 to focus on actual block production intervals. For incremental processing, limits data to recent partitions based on the maximum existing partition date plus a configurable lookback period.
- **Key fields**: `block_timestamp` (block creation time) and `block_number` (sequential block identifier)

### Component B: Sequential block pairing
- **Purpose**: Pairs each block with its immediate predecessor to enable time interval calculation
- **Logic**: Uses LAG window function ordered by `block_number` to retrieve the previous block's timestamp and number for each current block. This creates a dataset where each row contains both current and previous block timing information, enabling time difference calculations between consecutive blocks.
- **Key fields**: `previous_timestamp` (timestamp of preceding block) and `previous_block_number` (block number of preceding block)

### Component C: Block interval calculation
- **Purpose**: Computes actual time intervals between consecutive blocks
- **Logic**: Calculates time difference in milliseconds between current `block_timestamp` and `previous_timestamp` using timestamp difference functions. Filters to ensure only truly sequential blocks are included by verifying that `block_number` minus `previous_block_number` equals exactly 1, eliminating any gaps or non-sequential data. Truncates block timestamps to daily boundaries for aggregation purposes.
- **Key fields**: `block_time` (milliseconds between consecutive blocks) and daily truncated `timestamp`

### Final aggregation
- **Combining components**: Aggregates all block time intervals within each calendar day using average function to produce a single daily block time metric
- **Currency conversion**: Not applicable - metric is expressed in milliseconds
- **Time aggregation**: Groups by daily timestamp boundaries, calculating the mean of all block intervals within each 24-hour period
- **Final calculation**: Average of all millisecond intervals between consecutive blocks for each day, standardized with metadata including chain identifier (injective), market sector (blockchains_l1), business segment (blockchain), and product identifier (Injective Cosmos). The finalize_metric_block_time macro applies standard formatting and chain availability filtering to ensure data quality and consistency.

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

avg(block_timestamp - previous_block_timestamp)

InjectiveINJ

Block time

Block time

Competitive landscape

Chain breakdown