Aleph Zero EVM is powered by Arbitrum's AnyTrust protocol which uses a data availability committee (DAC) to store raw transaction data.

Aleph Zero EVM is an Ethereum layer 2 powered by Arbitrum Orbit tech stack. This dashboard does not include Aleph Zero WASM data.

AZERO tokenholders own and govern the protocol.

github

twitter

discord

website

Blockchains (L2)

Aleph Zero EVM

# Aleph Zero EVM Average transaction fee Methodology

## 1. Overview

The average transaction fee metric measures the mean cost per transaction on the Aleph Zero EVM blockchain, expressed in USD. This metric is calculated by dividing the total daily transaction fees by the total number of transactions executed on each day. It provides insight into the cost efficiency of the Aleph Zero network and helps users understand the typical expense of performing transactions on the platform.

## 2. Data sources

The calculation relies on three primary data sources:

- **Aleph Zero EVM transaction records**: Raw blockchain transaction data containing gas usage amounts, effective gas prices, transaction hashes, sender and recipient addresses, and block timestamps
- **End-of-day AZERO price feeds**: Daily AZERO token prices in USD from CoinGecko's market data API, using the 'aleph-zero' identifier
- **Address labeling database**: A curated database of known contract addresses and their associated labels for categorizing transaction destinations

## 3. Step-by-step calculation

### Component A: Individual transaction fee calculation
- **Purpose**: Calculate the gas fee for each individual transaction in native AZERO tokens
- **Logic**: For each transaction record, extract the `receipt_gas_used` (amount of gas consumed) and `receipt_effective_gas_price` (price per unit of gas). Multiply these values together to get the total gas cost in wei, then divide by 1e18 to convert from wei to AZERO tokens. This follows the standard Ethereum gas fee calculation model since Aleph Zero EVM is Ethereum-compatible
- **Key fields**: `receipt_gas_used`, `receipt_effective_gas_price`, and the calculated `l2_gas_fee_amount` field representing the transaction fee in AZERO tokens

### Component B: Daily fee aggregation and USD conversion
- **Purpose**: Sum all transaction fees by day and convert from AZERO to USD
- **Logic**: Group all transactions by day using timestamp truncation to daily boundaries. Sum the individual transaction fees calculated in Component A to get total daily fees in AZERO tokens. Join this aggregated data with end-of-day AZERO price feeds from CoinGecko, matching by timestamp. Multiply the daily AZERO fee totals by the corresponding daily USD price to convert fees to US dollars
- **Key fields**: Daily `timestamp`, aggregated `fees` in AZERO tokens, `price` from CoinGecko, and the final USD-denominated `fees`

### Component C: Daily transaction counting with labeling
- **Purpose**: Count the number of unique transactions per day and enrich with contract label information
- **Logic**: Group transactions by day and count distinct transaction hashes using approximate counting for efficiency. Extract the destination address (`to_address`) from each transaction and join with the address labeling database to categorize destinations as either labeled contracts or 'Unlabeled' addresses. This enrichment provides additional context about transaction patterns but doesn't affect the count itself
- **Key fields**: Daily `timestamp`, `transaction_count` using distinct `transaction_hash` values, `to_address` for labeling, and `contract_name` from the labels database

### Final aggregation
- **Combining components**: Join the daily USD fees from Component B with the daily transaction counts from Component C using the timestamp as the key. Both datasets are aggregated to the same daily grain, ensuring alignment
- **Currency conversion**: Fees are already converted to USD in Component B using end-of-day exchange rates, providing consistent valuation across time periods
- **Time aggregation**: All data is aggregated to daily boundaries using timestamp truncation, with both fees and counts calculated for the same 24-hour periods
- **Final calculation**: Calculate the average transaction fee by dividing the total daily fees (in USD) by the total daily transaction count using safe division. The safe division function handles edge cases where transaction count might be zero, preventing division errors and returning null or zero for such cases

The final metric represents the mean cost in USD that users pay per transaction on the Aleph Zero EVM network each day, providing a key indicator of network usage costs and efficiency.

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

Aleph Zero EVMAZERO

Archived

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown