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 Transaction count Methodology

## 1. Overview

The Heima transaction count metric measures the daily number of unique transactions processed across both Heima's native Substrate parachain and its EVM-compatible layer. This metric provides a comprehensive view of transaction activity by combining native blockchain operations with EVM-executed transactions, answering the question: "How many unique transactions occurred on Heima per day across all supported execution environments?"

## 2. Data sources

This metric relies on two primary blockchain data sources from the Heima protocol:

- **Native Substrate extrinsics**: Raw extrinsic records from Heima's parachain representing direct blockchain transactions and operations
- **EVM transaction events**: Parsed event logs from Heima's ethereum pallet, specifically `Executed` method events that represent EVM-compatible transactions processed through the protocol's EVM layer

## 3. Step-by-step calculation

### Component A: Transaction data unification
- **Purpose**: Combine native Substrate transactions and EVM-compatible transactions into a unified transaction dataset
- **Logic**: The calculation begins by collecting two distinct types of transaction data. Native Substrate transactions are extracted directly from extrinsic records with their original `extrinsic_id` values and tagged with chain identifier 'heima'. EVM-compatible transactions are identified from event logs where the `event_pallet` equals 'ethereum' and `event_method` equals 'Executed'. For EVM transactions, unique identifiers are created by concatenating the `extrinsic_id` with the `event_index` to ensure each EVM operation has a distinct identifier, and these are tagged with chain identifier 'heimaevm'
- **Key fields**: `block_timestamp` for timing, `extrinsic_id` for native transactions, concatenated `extrinsic_id-event_index` for EVM transactions, and `chain_id` for execution environment identification

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day and assign standardized metric metadata
- **Logic**: Transaction data is grouped by day using timestamp truncation to daily boundaries. The calculation counts distinct transaction identifiers to avoid double-counting any transactions. Each daily aggregate is assigned standardized metadata including timestamp grain as 'day', market sector as 'blockchains_l2', business segment as 'blockchain', and product identifier as null since this is a protocol-level metric
- **Key fields**: `timestamp` truncated to day, `transaction_count` from distinct counting, and various metadata fields for metric classification

### Final aggregation
- **Combining components**: The unified transaction data flows directly into the daily aggregation step without requiring separate joining of components
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries are established using timestamp truncation, with incremental processing that includes a configurable lookback period to handle late-arriving data
- **Final calculation**: The metric applies a finalization macro that validates the schema structure, ensures complete time series coverage by filling missing days with zero transaction counts using the 'fill_zeros' strategy, and applies chain availability filtering to exclude inactive chains. The final daily transaction count represents the total number of unique transactions across both Heima's native Substrate environment and EVM-compatible layer for each day.

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

Confirmed transactions added to the blockchain.

HeimaHEI

Transaction count

Transaction count

Competitive landscape

Chain breakdown