twitter

discord

website

github

Blockchains (L2)

peaq

# peaq Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average throughput capacity of the Peaq blockchain ecosystem by calculating the daily transaction volume divided by the number of seconds in a day. This metric captures activity across both the Peaq substrate chain and the Peaq EVM layer, providing a comprehensive view of the network's transaction processing capacity. The metric answers the business question: "What is the average transaction processing rate of the Peaq blockchain per second?"

## 2. Data sources

The calculation uses the following raw blockchain data sources:
- **Peaq substrate extrinsics**: Raw transaction data from the main Peaq substrate chain, containing all extrinsic (transaction) records with timestamps and unique identifiers
- **Peaq EVM events**: Parsed event logs from the Peaq EVM layer, specifically filtered for `Executed` events from the `ethereum` pallet that represent EVM transaction executions
- **Chain availability configuration**: Internal configuration data that determines which chain layers are currently active and should be included in calculations

## 3. Step-by-step calculation

### Component A: Transaction fact table creation
- **Purpose**: Creates a unified view of transactions across both Peaq substrate and EVM layers
- **Logic**: Extracts transactions from two distinct sources and standardizes them into a common format. From the substrate chain, it takes all extrinsics with their original identifiers. From the EVM layer, it filters event logs to only include `Executed` events from the `ethereum` pallet, which represent completed EVM transactions. Each EVM transaction gets a compound identifier combining the original `extrinsic_id` with the `event_index` to ensure uniqueness across the unified dataset.
- **Key fields**: `block_timestamp` for timing, `extrinsic_id` as the unique transaction identifier, and `chain_id` to distinguish between substrate ('peaq') and EVM ('Peaq EVM') layers

### Component B: Daily transaction count aggregation  
- **Purpose**: Counts total unique transactions per day across both chain layers
- **Logic**: Groups transactions by day using timestamp truncation and aggregates by counting distinct `extrinsic_id` values. The aggregation intentionally combines both substrate and EVM transactions into a unified daily count, treating the Peaq ecosystem as a single logical blockchain with multiple execution layers. Missing days are filled with zero values to maintain complete time series data.
- **Key fields**: Daily `timestamp`, `transaction_count` as the distinct count of transactions, and standardized metadata fields including `market_sector_id` set to 'blockchains_l2' and `business_segment_id` set to 'blockchain'

### Final aggregation
- **Combining components**: Daily transaction counts from both substrate and EVM layers are summed together to create a unified daily transaction total for the entire Peaq ecosystem
- **Currency conversion**: Not applicable - this is a transaction volume metric without currency conversion
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation, with the day determined by the `block_timestamp` of each transaction
- **Final calculation**: The transactions per second value is calculated by dividing the total daily transaction count by 86,400 (the number of seconds in a day), using safe division to handle potential division by zero scenarios. The result represents the average transaction processing rate across the entire 24-hour period.

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

Average confirmed user transactions added per second.

peaqPEAQ

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown