Validators process transactions and receive fees from users (supply-side fees).

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Average transaction fee Methodology

## 1. Overview

The Astar average transaction fee metric measures the mean fee paid per transaction on the Astar network on a daily basis, expressed in ASTR tokens. This metric provides insight into transaction cost efficiency by dividing total daily fees by total daily transaction count. Astar operates as a hybrid blockchain supporting both native Substrate transactions (Layer 1) and Ethereum-compatible EVM transactions (Layer 2), requiring fee collection from both execution layers.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Astar blockchain events**: Parsed blockchain events including `TransactionFeePaid` events from the `transactionPayment` pallet, `Withdraw` and `Deposit` events from the `balances` pallet, and `Executed` events from the `ethereum` pallet
- **Astar blockchain extrinsics**: Native Substrate transaction records containing extrinsic identifiers and execution metadata
- **End-of-day token price feeds**: ASTR token price data from CoinGecko for USD conversion (used in intermediate calculations but not the final average)

## 3. Step-by-step calculation

### Component A: Layer 1 fee extraction
- **Purpose**: Captures fees from native Substrate transactions on Astar's Layer 1
- **Logic**: Extracts `TransactionFeePaid` events from the `transactionPayment` pallet. Each event contains transaction fee and tip amounts in the event data array. The total fee is calculated by adding the base transaction fee (position 1 in event data) to the transaction tip (position 2 in event data). Raw amounts are converted from wei to ASTR tokens by dividing by 10^18.
- **Key fields**: `transaction_fee`, `transaction_tip`, `extrinsic_id`, `timestamp`

### Component B: Layer 2 fee extraction
- **Purpose**: Captures fees from Ethereum-compatible EVM transactions on Astar's Layer 2
- **Logic**: Processes `Withdraw` and `Deposit` events from the `balances` pallet that occur within the context of `ethereum` pallet execution. First identifies EVM transaction signers from `Executed` events in the `ethereum` pallet. Then matches `Withdraw` events (positive fees) and `Deposit` events (negative fees, inverted to positive) where the event signer address matches the original extrinsic signer. Fees are netted per extrinsic and converted from wei to ASTR by dividing by 10^18.
- **Key fields**: `transaction_fee`, `signer_address`, `extrinsic_id`, `event_method`, `timestamp`

### Component C: Transaction counting
- **Purpose**: Counts total unique transactions across both execution layers
- **Logic**: Combines native Substrate extrinsics (using direct `extrinsic_id`) with Ethereum-compatible transactions (identified by `Executed` events from the `ethereum` pallet, using concatenated `extrinsic_id` and `event_index` as unique identifiers). Uses approximate distinct count to handle potential duplicates and aggregates by day.
- **Key fields**: `extrinsic_id`, `block_timestamp`, `chain_id`

### Component D: Fee aggregation
- **Purpose**: Combines Layer 1 and Layer 2 fees into daily totals
- **Logic**: Unions the processed Layer 1 and Layer 2 fee streams, summing all fees by day. Both fee streams are tagged with chain identifiers ('astar' for L1, 'astarevm' for L2) and product identifier ('Astar Substrate').
- **Key fields**: `fees`, `timestamp`, `chain_id`, `product_id`

### Final aggregation
- **Combining components**: Daily fee totals are joined with daily transaction counts using inner join on timestamp to ensure both metrics exist for the same day
- **Currency conversion**: Fees remain in native ASTR tokens for the average calculation (USD conversion is applied separately in the underlying fee metrics but not used in the average)
- **Time aggregation**: Both fees and transaction counts are aggregated to daily boundaries using timestamp truncation
- **Final calculation**: Average transaction fee is calculated using safe division of total daily fees by total daily transaction count, handling cases where transaction count might be zero

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

AstarASTR

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown