Kinto batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Kinto is an L2 smart contract platform for decentralized applications on Ethereum with enforced account abstraction and KYC'd users. Kinto was founded by Ramon Recuero, Víctor Sánchez, and Alan Keegan and launched in 2024.

Kinto team & investors own and govern the protocol. Kinto’s investors include ParaFi Capital, Kyber Capital, The Spartan Group, etc.

github

twitter

discord

website

Blockchains (L2)

Kinto

# Kinto Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Kinto blockchain, expressed in milliseconds and aggregated daily. This metric provides insights into the blockchain's performance consistency and helps monitor network health. The calculation determines the time difference between each block and its predecessor, then averages these intervals across each day to produce a daily block time metric.

## 2. Data sources

- **Kinto blockchain block headers**: Raw block data from the Kinto blockchain containing block timestamps and sequential block numbers
- **Block timestamp data**: Precise timestamps indicating when each block was mined or validated
- **Block sequence data**: Sequential block numbers used to establish chronological ordering of blocks

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extract and prepare raw block timing data for interval calculations
- **Logic**: Raw Kinto blockchain block data is extracted, focusing on `block_timestamp` and `block_number` fields. The genesis block (block number 0) is excluded as it has a timestamp at the start of Unix time which would skew calculations. Block timestamps are cast to timestamp type and block numbers to integer type for consistent processing.
- **Key fields**: `block_timestamp` (when the block was created), `block_number` (sequential block identifier)

### Component B: Consecutive block pairing
- **Purpose**: Pair each block with its immediate predecessor to enable interval calculation  
- **Logic**: A lag window function ordered by ascending block number pairs each block with the timestamp of the previous block. This creates rows containing both the current block timestamp and the previous block timestamp, enabling time difference calculations between consecutive blocks.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: For each block-pair where a previous timestamp exists, the time difference is calculated in milliseconds between the current block timestamp and the previous block timestamp. Block timestamps are truncated to daily granularity to prepare for daily aggregation. Rows without a previous timestamp (the first block) are excluded.
- **Key fields**: `block_time` (milliseconds between blocks), `timestamp` (daily truncated timestamp)

### Component D: Daily aggregation
- **Purpose**: Average block times within each day and add metadata
- **Logic**: Block time intervals are grouped by the daily truncated timestamp and averaged to produce a single daily block time metric. Chain metadata is added including `chain_id` as 'kinto', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'. The `product_id` is set to null as this is a chain-level metric.
- **Key fields**: `block_time` (daily average in milliseconds), chain identification fields

### Final aggregation
- **Combining components**: All daily block time calculations flow through the sequence of CTEs without additional joining
- **Metric finalization**: The `finalize_metric_block_time` macro applies standardization, adds required metadata fields, and implements a fill_zeros strategy for missing data
- **Quality filtering**: A chain availability filter ensures only valid data periods are included in the final output
- **Final calculation**: The result is the average time in milliseconds between consecutive blocks for each day on the Kinto blockchain

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

avg(block_timestamp - previous_block_timestamp)

Kinto

Archived

Block time

Block time

Competitive landscape

Chain breakdown