Blast batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense). Bridge depositors deposit ETH or stablecoins to Blast and receive a yield from ETH staking or T-bill strategies.

Blast is an L2 smart contract platform for decentralized applications on Ethereum. Blast has an inherent yield generation mechanism, coming from ETH staking and RWA protocols. Blast was founded by Pacman and launched in 2023.

Blast team and investors currently own and govern the protocol. Blast's investors include Paradigm, Standard Crypto, Santiago, etc.

twitter

discord

website

Blockchains (L2)

Blast

# Blast Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Blast blockchain, expressed in milliseconds and aggregated daily. This metric indicates the blockchain's block production efficiency and network performance. The calculation analyzes consecutive block timestamps to determine the time elapsed between block creation, then averages these intervals within each day to provide a daily block time metric.

## 2. Data sources

- **Blast blockchain block headers**: Raw block data from the Blast blockchain including block timestamps, block numbers, gas usage metrics, and base fee information
- **Block metadata**: Additional block properties including uncle block references and network fee structures

## 3. Step-by-step calculation

### Component A: Block timestamp extraction
- **Purpose**: Extracts block timing data from raw Blast blockchain blocks
- **Logic**: Retrieves block timestamps and block numbers from Blast blockchain block headers. Filters out the genesis block (block 0) since it has an artificial timestamp at the start of Unix time that would skew calculations. For incremental processing, applies date-based filtering to process only recent blocks within the specified lookback window.
- **Key fields**: `block_timestamp` (when the block was mined), `block_number` (sequential block identifier)

### Component B: Consecutive block pairing
- **Purpose**: Creates pairs of consecutive blocks to enable time difference calculations
- **Logic**: Uses a window function with LAG to obtain the timestamp of the previous block for each current block, ordered by block number. This creates pairs of consecutive blocks where each row contains both the current block timestamp and the previous block timestamp.
- **Key fields**: `block_timestamp` (current block), `previous_timestamp` (previous block timestamp via LAG function), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Calculates the actual time elapsed between consecutive blocks
- **Logic**: Computes the time difference between each block and its predecessor using timestamp difference functions. Measures the interval in milliseconds to provide precise timing measurements. Filters out records where the previous timestamp is null (typically the first block in the dataset).
- **Key fields**: `timestamp` (daily boundary for aggregation), `block_time` (millisecond difference between consecutive blocks)

### Final aggregation
- **Combining components**: Groups block time intervals by day using timestamp truncation to daily boundaries
- **Currency conversion**: Not applicable for time-based metrics
- **Time aggregation**: Truncates block timestamps to daily boundaries and groups all block intervals within each day
- **Final calculation**: Applies average function to all block time intervals within each day to produce a single daily average block time value in milliseconds. The result includes standard metadata fields for chain identification and market classification, with the final metric representing the average time between blocks for each day on the Blast blockchain.

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

avg(block_timestamp - previous_block_timestamp)

BlastBLAST

Archived

Block time

Block time

Competitive landscape

Chain breakdown