website

twitter

github

Blockchains (L2)

Aventus

# Aventus Average transaction fee Methodology

## 1. Overview

Average transaction fee measures the average fee users pay per transaction. It reflects how much it typically costs to use the network. The metric is calculated by dividing the total daily transaction fees by the total daily transaction count. Both native Aventus chain transactions and EVM-compatible transactions are captured to provide a comprehensive view of network activity.

## 2. Data sources

- **Blockchain events**: `TransactionFeePaid` events, `Executed` events from the `evm` pallet, and `Withdraw` and `Deposit` events from the `balances` pallet, covering Aventus
- **External data**: End-of-day price feeds for the Aventus asset

## 3. Step-by-step calculation

### Component A: Layer 1 fee extraction

- **Purpose**: Extract and normalize transaction fees paid on the native Aventus chain
- **Logic**: `TransactionFeePaid` events are parsed from successful transactions. The base fee `amount` and optional `tip` are extracted from the event data. Both values are normalized by decimal precision, and the total fee per transaction is calculated as the sum of the base fee and the tip.
- **Key fields**: `amount`, `tip`, `block_timestamp`

### Component B: Layer 2 fee extraction

- **Purpose**: Extract and normalize transaction fees paid on the EVM-compatible layer of Aventus
- **Logic**: `Withdraw` and `Deposit` events are parsed from the `balances` pallet where the pallet is identified as `evm`. Signer addresses are mapped to their corresponding EVM accounts using account dimension data. Transactions are filtered to retain only those where the signer of the balance change matches the transaction signer. Net fees are calculated by subtracting deposits from withdrawals, normalized by decimal precision, and aggregated by transaction.
- **Key fields**: `transaction_fee`, `signer_address`, `extrinsic_id`

### Component C: USD conversion

- **Purpose**: Convert native asset fees to USD values
- **Logic**: Daily fee totals from both Layer 1 and Layer 2 are aggregated. Native asset amounts are multiplied by end-of-day price feeds for the Aventus asset to determine the daily fee total in USD.
- **Key fields**: `fees`, `price_usd`

### Component D: Transaction counting

- **Purpose**: Count the total number of transactions executed on the network
- **Logic**: Transactions are aggregated from native extrinsics and EVM-compatible events. For native transactions, distinct extrinsic identifiers are counted. For EVM transactions, distinct combinations of extrinsic identifiers and event indexes from `Executed` events are counted. The transaction counts from both sources are summed to calculate the total daily transaction count.
- **Key fields**: `extrinsic_id`, `event_index`, `block_timestamp`

### Component E: Average fee calculation

- **Purpose**: Calculate the average transaction fee in USD
- **Logic**: Daily fee totals in USD are divided by the daily transaction count. Safe division is applied to prevent division-by-zero errors, returning null if the transaction count is zero.
- **Key fields**: `fees`, `transaction_count`

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

AventusAVT

Archived

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown