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

Heima is a specialized identity and data verification blockchain powered by Polkadot Relay chain.

HEI holders own and govern the protocol. Heima’s investors include LD Capital, Digital Renaissance, Signum Capital, and others.

website

twitter

github

discord

etherscan

Blockchains (L2)

Heima

# Heima Average transaction fee Methodology

## 1. Overview

The Heima average transaction fee metric measures the mean cost per transaction on the Heima blockchain on a daily basis. This metric is calculated by dividing the total daily transaction fees (in USD) by the total number of transactions executed that day. The calculation accounts for both Layer 1 (substrate-based) and Layer 2 (EVM-based) transactions on the Heima network, providing a comprehensive view of transaction costs across the entire ecosystem.

## 2. Data sources

The calculation relies on several raw blockchain data sources:

- **Heima blockchain event logs**: Parsed events including `TransactionFeePaid` events for L1 fees, `Executed` events for EVM transaction identification, `Withdraw` and `Deposit` events for L2 fee calculation, and `NewAccount` events for account mapping
- **Heima blockchain transaction data**: Extrinsic records containing L1 transaction identifiers and execution details
- **End-of-day price feeds**: LIT token price data from CoinGecko for USD conversion
- **Account mapping data**: Derived mappings between Substrate parachain addresses and EVM addresses using cryptographic hash functions

## 3. Step-by-step calculation

### Component A: L1 transaction fees
- **Purpose**: Calculate fees for substrate-based transactions on Heima L1
- **Logic**: Extract `TransactionFeePaid` events from successful transactions, sum the `amount` and `tip` fields from the event data, and scale by dividing by 1e18 to account for LIT token decimals. Aggregate these fees by day for all L1 transactions.
- **Key fields**: Event data contains `amount` (base transaction fee) and `tip` (optional additional fee), both stored as bignumeric values requiring decimal scaling

### Component B: L2 transaction fees  
- **Purpose**: Calculate fees for EVM-based transactions on Heima L2
- **Logic**: Identify EVM transactions through `Executed` events in the ethereum pallet, then match these with corresponding `Withdraw` and `Deposit` events in the balances pallet. Use account mapping to ensure the signer of the balance events matches the EVM transaction executor. Sum withdraw amounts (positive) and subtract deposit amounts (negative) to get net fees, then aggregate by day.
- **Key fields**: EVM `Executed` events contain `signer_address`, balance events contain transaction fee amounts, account mapping links `parachain_account` to `evm_account`

### Component C: Account mapping
- **Purpose**: Create mappings between Substrate parachain addresses and EVM addresses for L2 fee attribution
- **Logic**: Extract parachain accounts from system `NewAccount` events, decode SS58-encoded addresses to hex format using base58 decoding, then derive corresponding EVM addresses by computing keccak256 hash of the string "evm:" concatenated with the substrate hex address and taking the last 20 bytes
- **Key fields**: Parachain account strings require SS58 decoding, derived EVM addresses enable proper fee attribution across address formats

### Component D: Transaction counting
- **Purpose**: Count total daily transactions across both L1 and L2
- **Logic**: Count distinct L1 transactions using `extrinsic_id` from extrinsic records, count distinct L2 transactions using `extrinsic_id` concatenated with `event_index` from ethereum `Executed` events. Union both sources and aggregate daily counts.
- **Key fields**: L1 uses `extrinsic_id`, L2 uses combined `extrinsic_id-event_index` identifier to ensure uniqueness

### Component E: USD conversion
- **Purpose**: Convert LIT token amounts to USD values using market prices
- **Logic**: Apply end-of-day LIT token prices from CoinGecko to all fee amounts calculated in Components A and B. Match prices to transaction dates and multiply fee amounts by corresponding exchange rates.
- **Key fields**: Daily `timestamp` for price matching, `fees` amounts in LIT tokens, converted `fees` in USD

### Final aggregation
- **Combining components**: Sum total daily fees in USD from both L1 and L2 sources, sum total daily transaction counts from both L1 and L2 sources
- **Currency conversion**: All fees converted to USD using end-of-day LIT token prices before aggregation
- **Time aggregation**: All data aggregated to daily boundaries using timestamp truncation to day granularity  
- **Final calculation**: Divide total daily fees by total daily transaction count using safe division to handle days with zero transactions, apply zero-fill strategy for missing days to ensure continuous time series

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

HeimaHEI

Average transaction fee

Average transaction fee

Competitive landscape

Chain breakdown