twitter

etherscan

website

Blockchains (L2)

Unichain

# Unichain Average transaction fee Methodology

## 1. Overview

The Unichain average transaction fee metric measures the mean cost per transaction on the Unichain blockchain, expressed in USD. This metric helps evaluate the network's cost-efficiency for users by dividing the total daily transaction fees by the total number of transactions executed each day. The calculation accounts for Unichain's dual-layer fee structure, which includes both L2 execution fees and L1 data availability fees.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Unichain transaction records**: Complete transaction data from the Unichain blockchain including transaction hashes, gas usage metrics, gas prices, and Layer 1 fee components
- **End-of-day token price feeds**: USD pricing data for ETH (the native token used for transaction fees on Unichain)
- **Token metadata**: Standard token information including the canonical ETH token address (`0x4200000000000000000000000000000000000006`) used for fee calculations

## 3. Step-by-step calculation

### Component A: Transaction fee calculation

- **Purpose**: Calculate the total fee paid for each transaction in USD
- **Logic**: Extract raw transaction data including gas usage metrics (`gas_used`), gas prices (`gas_price`), and Layer 1 fee components (`l1_gas_used`, `l1_gas_price`, `l1_fee_scalar`). Calculate the L2 execution fee by multiplying gas used by gas price and dividing by 1e18 to correct for Wei decimals. Calculate the L1 data availability fee by multiplying L1 gas used, L1 gas price, and L1 fee scalar, then dividing by 1e18. Sum the L2 and L1 fees to get the total transaction fee in ETH. Convert the ETH amounts to USD using end-of-day price feeds
- **Key fields**: Transaction hash (`transaction_hash`), block timestamp (`block_timestamp`), gas metrics (`gas_used`, `gas_price`), L1 fee components (`l1_gas_used`, `l1_gas_price`, `l1_fee_scalar`), and calculated fee amounts (`l2_gas_fee`, `l1_gas_fee`)

### Component B: Daily fee aggregation

- **Purpose**: Sum all transaction fees for each day
- **Logic**: Group all calculated transaction fees by day using timestamp truncation to daily boundaries. Sum the USD-converted fees for all transactions within each day to get total daily fee revenue
- **Key fields**: Daily timestamp (`timestamp`), aggregated fee total (`fees`)

### Component C: Daily transaction counting

- **Purpose**: Count the total number of unique transactions per day
- **Logic**: Group transaction records by day using the same daily timestamp boundaries. Count distinct transaction hashes using approximate counting for efficiency to determine the total number of unique transactions executed each day
- **Key fields**: Daily timestamp (`timestamp`), transaction count (`transaction_count`)

### Final aggregation

- **Combining components**: Join the daily fee totals with daily transaction counts using the timestamp as the key, ensuring both metrics cover the same time periods
- **Currency conversion**: All fees are already converted to USD during the fee calculation step using end-of-day ETH price feeds
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with all calculations performed at the daily grain
- **Final calculation**: Divide the total daily fees by the total daily transaction count using safe division to handle edge cases where transaction count might be zero, resulting in the average transaction fee in USD per day

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

UnichainUNI

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown