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 Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the AlephZero EVM blockchain over a daily period. This metric provides insight into the network's transaction throughput and activity levels. The calculation takes the total number of unique transactions in a day and divides by 86,400 seconds to derive the average TPS for that day.

## 2. Data sources

- **AlephZero EVM transaction records**: Raw blockchain transaction data including block timestamps, transaction hashes, sender addresses (`from_address`), recipient addresses (`to_address`), gas prices, and gas usage amounts
- **Account labeling dataset**: Address labels for AlephZero accounts that identify contract names and account titles for known addresses
- **Time constants**: System configuration defining seconds per day (86,400) used for TPS conversion

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw transaction data from the AlephZero EVM blockchain
- **Logic**: Raw transaction records are pulled from AlephZero EVM blockchain data, including block timestamps, transaction hashes, sender and recipient addresses, gas prices, and gas usage. The data is standardized with chain identifier set to 'Aleph Zero EVM', market sector as 'blockchains_l2', and business segment as 'blockchain'. Gas fees are calculated by multiplying gas price by gas used amount and dividing by 1e18 to convert from wei to native token units. Product ID is set to null for this blockchain-level metric.
- **Key fields**: `block_timestamp` for daily grouping, `transaction_hash` for unique counting, `from_address` and `to_address` for transaction flow, `gas_price` and `gas_used_amount` for fee calculations

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day and enrich with address labels
- **Logic**: Transaction timestamps are truncated to day level using timestamp truncation. Transactions are grouped by day, timestamp grain ('day'), chain ID, market sector, business segment, product ID, and recipient address (`to_address`). Approximate distinct count is applied to `transaction_hash` to count unique transactions while handling potential duplicates efficiently. The aggregated data is then enriched with account labels by left joining recipient addresses to the account labeling dataset. Addresses without labels are categorized as 'Unlabeled'.
- **Key fields**: `timestamp` (daily), `transaction_count` (approximate distinct), `contract_name` (from labels or 'Unlabeled')

### Component C: Schema finalization and gap filling
- **Purpose**: Ensure consistent schema and fill missing data points
- **Logic**: The finalize_metric_transaction_count macro is applied to validate data schema, ensure proper ID fields, and fill any missing days with zero transaction counts. This ensures consistent daily time series data with no gaps. The fill strategy uses zeros for missing periods rather than null values or interpolation.
- **Key fields**: Standardized metric schema fields with consistent data types and complete daily coverage

### Final aggregation
- **Combining components**: Daily transaction counts are summed across all contract types and addresses for each day to get total network transaction volume
- **TPS conversion**: The final transactions per second calculation divides the daily transaction count by 86,400 seconds (using the `seconds_in_day` variable) with safe division to prevent errors
- **Time boundaries**: Data is filtered to exclude dates beyond 2025-09-17 to prevent inclusion of incomplete or future-dated records
- **Final calculation**: TPS = Daily Transaction Count ÷ 86,400 seconds, providing the average number of transactions processed per second during that 24-hour period

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

Average confirmed user transactions added per second.

Aleph Zero EVMAZERO

Archived

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown