website

twitter

discord

github

Blockchains (L1)

Sonic

# Sonic Average transaction fee Methodology

## 1. Overview

The average transaction fee metric measures the mean cost per transaction on the Sonic blockchain, calculated by dividing total daily transaction fees by the total number of transactions for each day. This metric provides insight into the economic efficiency and cost structure of using the Sonic network, helping users understand the typical expense of executing transactions on this blockchain.

## 2. Data sources

The calculation relies on several key data sources:
- **Sonic blockchain transaction records**: Raw transaction data including block timestamps, transaction hashes, gas usage amounts, effective gas prices, sender and recipient addresses
- **End-of-day token price feeds**: Price data for Sonic's native token (S) to convert gas fees from native tokens to USD values  
- **Token metadata**: Information about Sonic's native token including the contract address `0x039e2fb66102314ce7b64ce5ce3e5183bc94ad38` and symbol `S`

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Extract and standardize transaction information from raw Sonic blockchain data
- **Logic**: Raw transaction records are processed to extract key fields including block timestamps, transaction hashes, gas usage amounts, and effective gas prices. The `effective_gas_price` values are normalized by dividing by 10^18 to convert from wei-equivalent units to standard token units. All transactions are tagged with the Sonic chain identifier and native token information.
- **Key fields**: `block_timestamp`, `transaction_hash`, `gas_used`, `effective_gas_price`, `from_address`, `to_address`

### Component B: Daily fee calculation  
- **Purpose**: Calculate total transaction fees paid per day in native Sonic tokens
- **Logic**: For each transaction, the fee amount is calculated by multiplying `gas_used` by `effective_gas_price`. These individual transaction fees are then summed by day using timestamp truncation to day granularity. The daily fee totals represent the aggregate cost of all transactions on the Sonic network for each day.
- **Key fields**: `timestamp` (truncated to day), `fee_amount` (sum of gas_used × effective_gas_price)

### Component C: USD conversion
- **Purpose**: Convert daily fee amounts from native Sonic tokens to USD values
- **Logic**: Daily fee totals in native Sonic tokens are converted to USD using end-of-day price feeds for the Sonic token. This conversion uses the `convert_to_usd_and_correct_decimals` transformation which applies appropriate exchange rates and handles decimal precision for accurate USD representation.
- **Key fields**: `fees` (USD-denominated fee amounts)

### Component D: Transaction count calculation
- **Purpose**: Count the total number of unique transactions per day
- **Logic**: Using the same processed transaction data, distinct transaction hashes are counted and grouped by day. This ensures each unique transaction is counted exactly once, avoiding any potential double-counting from data processing. The daily transaction counts represent the total volume of transaction activity on Sonic.
- **Key fields**: `timestamp` (truncated to day), `transaction_count` (count of distinct transaction_hash)

### Final aggregation
- **Combining components**: The daily fee totals (in USD) and daily transaction counts are joined on the timestamp field to align the data by day
- **Currency conversion**: All fee amounts are already converted to USD in the fee calculation component using end-of-day exchange rates
- **Time aggregation**: Both fees and transaction counts use day-level granularity with timestamps truncated to the start of each day
- **Final calculation**: The average transaction fee is calculated by dividing the total daily fees in USD by the daily transaction count using safe division to handle cases where transaction count might be zero, preventing division errors and returning null for days with no transactions

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

SonicS

Archived

Average transaction fee

Average transaction fee

Competitive landscape