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 Transaction count Methodology

## 1. Overview

The Blast transaction count metric measures the daily number of unique transactions processed on the Blast blockchain, categorized by recipient contract or address. This metric provides insight into network activity and usage patterns by counting distinct transaction hashes per day and enriching the data with human-readable contract labels.

## 2. Data sources

- **Blast blockchain transaction records**: Raw transaction data from the Blast blockchain containing transaction hashes, block timestamps, sender and receiver addresses, gas usage information, and other transaction metadata
- **Address labeling data**: Contract and account labels specifically for the Blast chain, providing human-readable names for known addresses, contracts, and protocols

## 3. Step-by-step calculation

### Component A: Daily transaction aggregation
- **Purpose**: Aggregates raw Blast transactions into daily counts by recipient address
- **Logic**: Raw Blast transaction records are filtered and grouped by day using timestamp truncation to daily boundaries. Transactions are then grouped by `to_address` (recipient) and the distinct count of `transaction_hash` values is calculated to ensure each unique transaction is counted exactly once. The aggregation includes metadata fields identifying this as Blast chain data with appropriate market sector and business segment classifications.
- **Key fields**: `block_timestamp` (truncated to day), `to_address` (recipient address), `transaction_hash` (for distinct counting), along with static metadata fields for chain identification

### Component B: Address label enrichment  
- **Purpose**: Enhances transaction counts with human-readable contract and address names
- **Logic**: The daily transaction counts are joined with Blast-specific address labeling data using the `to_address` field. When a matching label is found, the `account_title` provides a descriptive name for the contract or address. For addresses without labels, the system defaults to 'Unlabeled' to ensure all transaction counts are preserved in the final output.
- **Key fields**: `to_address` (for joining), `account_title` (label name), with the result mapped to `contract_name`

### Final aggregation
- **Combining components**: The labeled transaction counts are processed through a standardization macro that validates the data schema, ensures consistent field naming and data types, and applies business rules for metric formatting
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily time boundaries are established by truncating block timestamps to day precision, ensuring consistent 24-hour periods for counting
- **Final calculation**: The final metric value represents the distinct count of transaction hashes per day per recipient address/contract, enriched with descriptive labels and filtered to exclude periods when the Blast chain was not operational. Missing days are filled with zero values to maintain continuous time series data.

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

Confirmed transactions added to the blockchain.

BlastBLAST

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown