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 Average transaction fee Methodology

## 1. Overview

The average transaction fee metric measures the mean cost per transaction on the Energy Web blockchain, expressed in USD. This metric helps assess the economic accessibility and usage patterns of the Energy Web network by calculating the typical cost users pay to execute transactions. The calculation divides the total daily transaction fees by the total daily transaction count to derive an average fee per transaction.

## 2. Data sources

The methodology utilizes several key data sources:

- **Energy Web blockchain events**: Raw event logs from the Energy Web blockchain, specifically `TransactionFeePaid` events from the `transactionPayment` pallet that record fee payments for each transaction
- **Energy Web blockchain extrinsics**: Complete transaction records (called "extrinsics" in Substrate-based chains like Energy Web) that represent all blockchain operations and state changes
- **External price data**: End-of-day price feeds from CoinGecko for Energy Web Token (EWT) to enable USD conversion using the identifier 'energy-web-token'
- **Token metadata**: Information about Energy Web Token including decimal precision (18 decimals) and chain classification data

## 3. Step-by-step calculation

### Component A: Transaction fee extraction and aggregation

- **Purpose**: Extract and aggregate all transaction fees paid on Energy Web chain by day
- **Logic**: The system processes `TransactionFeePaid` events from the Energy Web `transactionPayment` pallet. Each event contains JSON-formatted data where fee information is stored in array positions - the base transaction fee in position [1] and the transaction tip in position [2]. These values are extracted, combined to create the total transaction fee, and converted from wei (the smallest unit with 18 decimal places) to EWT tokens by dividing by 10^18. The fees are then aggregated by day using timestamp truncation to daily boundaries.
- **Key fields**: `event_data` array containing fee amounts, `transaction_fee` and `transaction_tip` values, `extrinsic_id` for transaction identification

### Component B: Transaction count aggregation  

- **Purpose**: Count the total number of unique transactions processed on Energy Web chain per day
- **Logic**: The system processes all Energy Web extrinsics (transactions) by counting distinct `extrinsic_id` values. Each extrinsic represents a single transaction or blockchain operation. The counts are aggregated daily using timestamp truncation on the `block_timestamp` field to align with the fee data timeframe.
- **Key fields**: `extrinsic_id` for unique transaction identification, `block_timestamp` for daily grouping, `chain_id` for Energy Web identification

### Component C: USD conversion

- **Purpose**: Convert EWT-denominated fees to USD values for standardized reporting
- **Logic**: The aggregated daily fees in EWT tokens are converted to USD using end-of-day price feeds from CoinGecko. The conversion uses the 'energy-web-token' identifier to fetch EWT prices and applies them to the daily fee totals.
- **Key fields**: `fees` in EWT tokens, CoinGecko price data, converted USD values

### Final aggregation

- **Combining components**: The total daily fees (in USD) are joined with daily transaction counts using the timestamp as the common key. Both datasets use the same daily time boundaries to ensure alignment.
- **Currency conversion**: All fees are converted to USD using end-of-day EWT prices from CoinGecko before the average calculation
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, ensuring consistent time alignment between fee and transaction count data
- **Final calculation**: The average transaction fee is calculated by dividing the total daily fees in USD by the total daily transaction count using safe division (which handles division by zero by returning null). The system applies gap-filling logic to ensure continuous time series data, filling missing days with zero values. Chain availability filters are applied to respect data availability windows for the Energy Web network.

## Critical guidelines

The methodology includes several important data quality measures:
- Safe division prevents errors when dividing by zero transaction counts
- Gap filling ensures continuous time series without missing dates
- Chain availability filters respect the actual operational history of Energy Web chain
- Decimal precision is carefully maintained throughout the calculation pipeline
- Both base transaction fees and tips are included in the total fee calculation to capture the complete cost of transaction execution

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

Energy Web XEWT

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown