Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Energy Web X is energy blockchain ecosystem powered by Polkadot Relay chain.

website

twitter

github

etherscan

Blockchains (L2)

Energy Web X

# Energy Web X Transactions per second Methodology

## 1. Overview

The Energy Web transactions per second metric measures the average daily transaction throughput on the Energy Web blockchain. It calculates the number of unique transactions (extrinsics) processed per second by taking the total daily transaction count and dividing by the number of seconds in a day (86,400). This metric provides insight into the blockchain's daily transaction processing capacity and network utilization.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Energy Web extrinsics**: Raw blockchain transaction data from the Energy Web network, including block timestamps and unique transaction identifiers (extrinsic IDs)
- **Energy Web blockchain records**: Transaction-level data that captures all executed operations on the Energy Web Substrate-based blockchain

## 3. Step-by-step calculation

### Component A: Raw transaction extraction
- **Purpose**: Extract and standardize raw Energy Web transaction data
- **Logic**: Retrieves extrinsics data from the Energy Web blockchain, casting the `block_timestamp` field to timestamp format and `extrinsic_id` to string format for consistent processing. Each record represents a unique transaction executed on the Energy Web network. The `chain_id` is set to 'energyweb' to identify the blockchain network.
- **Key fields**: `block_timestamp` (when the transaction was processed), `extrinsic_id` (unique transaction identifier), `chain_id` (blockchain identifier)

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day to establish daily transaction volume
- **Logic**: Groups transactions by day using timestamp truncation to daily granularity. Counts distinct `extrinsic_id` values to determine the total number of unique transactions processed each day. Sets metadata fields including `timestamp_grain` as 'day', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'. The `product_id` is set to null as this is a network-level metric.
- **Key fields**: `timestamp` (daily date), `transaction_count` (distinct count of extrinsic IDs), `chain_id`, various metadata fields for categorization

### Final aggregation
- **Combining components**: The daily transaction counts are passed directly from the transaction count component to the final calculation
- **Currency conversion**: Not applicable - this is a transaction volume metric, not a financial metric
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day level. Missing days are filled with zero values to ensure complete time series data
- **Final calculation**: The transactions per second rate is calculated by dividing the daily transaction count by 86,400 (the number of seconds in a day). This provides the average transaction processing rate per second for each day. The calculation uses safe division to handle any potential division errors. Chain availability filters are applied to ensure data quality and completeness.

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

Average confirmed user transactions added per second.

Energy Web XEWT

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown