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 Transactions per second Methodology

## 1. Overview

The transactions per second (TPS) metric measures the average daily transaction throughput for the Heima blockchain network. This metric combines transactions from both Heima's native substrate chain and its EVM-compatible layer, providing a unified view of network activity. The calculation aggregates all daily transactions and divides by the number of seconds in a day (86,400) to produce an average transactions per second value.

## 2. Data sources

- **Heima substrate extrinsics**: Native substrate blockchain transactions from the Heima parachain, containing transaction metadata including timestamps and unique extrinsic identifiers
- **Heima EVM events**: Ethereum Virtual Machine transactions executed on Heima's EVM layer, captured as events from the ethereum pallet with `Executed` method calls
- **Time boundaries**: Daily aggregation periods based on block timestamps for consistent time-based grouping

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Combines transaction data from both Heima's substrate and EVM layers into a unified transaction dataset
- **Logic**: Extracts substrate transactions using `extrinsic_id` as the transaction identifier and labels them with `heima` chain identifier. Separately extracts EVM transactions by filtering events for the ethereum pallet with `Executed` method, creating unique transaction identifiers by concatenating `extrinsic_id` and `event_index`, and labeling them with `heimaevm` chain identifier. The two transaction sources are combined through a union operation to create a complete transaction dataset.
- **Key fields**: `block_timestamp` for timing, `extrinsic_id` for substrate transaction identification, concatenated `extrinsic_id` and `event_index` for EVM transaction identification, and `chain_id` for distinguishing transaction types

### Component B: Daily transaction aggregation  
- **Purpose**: Aggregates transaction counts on a daily basis for each chain type
- **Logic**: Groups transactions by day using timestamp truncation to day boundaries. Counts distinct transaction identifiers to avoid double-counting any transactions. Applies business segment classification as `blockchain` and market sector as `blockchains_l2`. Sets product identifier to null since this represents chain-level activity rather than specific product usage. Ensures complete daily time series by filling any missing dates with zero transaction counts.
- **Key fields**: `timestamp` truncated to daily boundaries, `transaction_count` as distinct count of transaction identifiers, `chain_id` for substrate vs EVM distinction, and classification fields for business categorization

### Component C: Transactions per second calculation
- **Purpose**: Converts daily transaction counts into average transactions per second values
- **Logic**: Sums transaction counts across both substrate and EVM chains to get total daily Heima network activity. Divides the total daily transaction count by 86,400 seconds (the number of seconds in a day) using safe division to handle any potential zero denominators. Aggregates results with `unknown` chain identifier since the final metric represents combined network activity rather than individual chain performance.
- **Key fields**: Aggregated `transaction_count` from both chains, `transactions_per_second` as the calculated average, and consolidated chain identifier

### Final aggregation
- **Combining components**: Daily transaction counts from both substrate and EVM sources are summed together to represent total network activity, then divided by seconds in a day to calculate average TPS
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries based on block timestamps, with zero-filling for any missing dates to maintain continuous time series
- **Final calculation**: Total daily transactions across both Heima substrate and EVM layers divided by 86,400 seconds equals average transactions per second for that day

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

Average confirmed user transactions added per second.

HeimaHEI

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown