website

twitter

discord

github

Blockchains (L1)

Sonic

# Sonic Transaction count Methodology

## 1. Overview

The Sonic transaction count metric measures the total number of unique transactions occurring on the Sonic blockchain on a daily basis. This metric answers the question "How much transaction activity is happening on Sonic?" and serves as a fundamental indicator of blockchain usage and adoption. The calculation uses a simple but robust approach: counting distinct transaction hashes from raw Sonic blockchain data, grouped by day and recipient address.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Sonic blockchain transaction records**: Complete transaction data from the Sonic blockchain including transaction hashes, sender and receiver addresses, block timestamps, and execution details
- **Sonic block metadata**: Block-level information including block numbers and timestamps used for daily aggregation boundaries
- **Sonic transaction execution data**: Gas usage and gas price information from transaction receipts

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Standardize and prepare raw Sonic blockchain transaction data for counting
- **Logic**: Extract transaction records from raw Sonic blockchain data and apply consistent data type casting. Each transaction record includes the unique `transaction_hash`, `block_timestamp` for time boundaries, `from_address` and `to_address` for transaction participants, and execution details like `gas_used` and `effective_gas_price`. The system also enriches each record with Sonic-specific metadata including the native token address and symbol
- **Key fields**: `transaction_hash` serves as the unique identifier, `block_timestamp` provides the time dimension, `to_address` enables recipient-level analysis, and gas fields capture execution costs

### Component B: Daily aggregation
- **Purpose**: Group transactions by day and count unique transactions per recipient
- **Logic**: Truncate `block_timestamp` values to daily boundaries using day-level granularity. Group all transactions by the truncated timestamp, chain identifier, market sector, business segment, and recipient address (`to_address`). For each group, count the number of distinct `transaction_hash` values to avoid double-counting any transactions that might appear multiple times in the raw data. Set standard metadata fields including chain identifier as sonic, market sector as blockchains_l1, and business segment as blockchain
- **Key fields**: `timestamp` as the daily boundary, `transaction_count` as the distinct count of transaction hashes, `to_address` for recipient-level granularity

### Final aggregation
- **Combining components**: The daily aggregation results are processed through the finalize metric transaction count macro which standardizes the output schema, validates all identifier fields, and ensures complete time series coverage
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring all transactions within a 24-hour period are grouped together
- **Final calculation**: The final metric value represents the distinct count of transaction hashes occurring on each day, segmented by recipient address, providing both network-wide and address-specific transaction volume measurements

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

Confirmed transactions added to the blockchain.

SonicS

Archived

Transaction count

Transaction count

Competitive landscape