website

twitter

github

Blockchains (L2)

Invarch

# Invarch Transaction count Methodology

## 1. Overview

The transaction count metric measures the total number of unique transactions processed daily on the InArch blockchain. This metric captures both native substrate transactions and EVM-compatible transactions executed on InArch's dual execution environment, providing a comprehensive view of network transaction activity. The calculation aggregates distinct transactions by day to track daily usage patterns and network growth.

## 2. Data sources

The calculation relies on two primary data sources from the InArch blockchain:

- **Native substrate extrinsics**: Raw transaction data from InArch's substrate-based blockchain, containing native substrate transactions with block timestamps and unique extrinsic identifiers
- **EVM execution events**: Blockchain event logs from InArch's EVM compatibility layer, specifically `Executed` events from the `evm` pallet that represent completed EVM transactions, including block timestamps, extrinsic identifiers, and event indices

## 3. Step-by-step calculation

### Component A: Native substrate transactions
- **Purpose**: Captures all native substrate transactions on InArch
- **Logic**: Extracts all substrate extrinsics with their block timestamps and unique identifiers. Each extrinsic represents a direct substrate transaction. Records are labeled with chain identifier 'invarch' to distinguish from EVM transactions
- **Key fields**: `block_timestamp` for timing, `extrinsic_id` for unique transaction identification, and chain labeling for transaction type classification

### Component B: EVM transactions  
- **Purpose**: Captures EVM-compatible transactions executed on InArch's EVM layer
- **Logic**: Filters blockchain events to identify completed EVM transactions by selecting events where the pallet is 'evm' and method is 'Executed'. Creates composite transaction identifiers by concatenating the original `extrinsic_id` with the `event_index` to ensure uniqueness when multiple EVM events occur within a single extrinsic. Records are labeled with chain identifier 'invarchevm' to distinguish from native substrate transactions
- **Key fields**: `block_timestamp` for timing, composite `extrinsic_id` created from original extrinsic ID and event index, and chain labeling for transaction type classification

### Component C: Transaction unification
- **Purpose**: Combines both transaction types into a unified dataset
- **Logic**: Unions the native substrate transactions and EVM transactions into a single dataset, maintaining the distinct chain identifiers to preserve transaction type information while creating a comprehensive view of all InArch network activity
- **Key fields**: Unified `block_timestamp`, `extrinsic_id` (native or composite), and `chain_id` for transaction type tracking

### Final aggregation
- **Combining components**: The unified transaction dataset is grouped by daily time boundaries using timestamp truncation to the day level
- **Time aggregation**: Block timestamps are truncated to day boundaries to create daily aggregation periods, ensuring consistent daily metrics regardless of exact transaction timing
- **Transaction counting**: Applies distinct counting on `extrinsic_id` values within each day and chain combination to ensure each unique transaction is counted exactly once, preventing double-counting of transactions that might appear multiple times in the raw data
- **Final calculation**: The result is the count of distinct transactions per day, categorized by chain type ('invarch' for native substrate, 'invarchevm' for EVM), with additional metadata including market sector classification as 'blockchains_l2' and business segment as 'blockchain'

The final metric represents the total number of unique transactions processed daily on the InArch network, combining both native substrate and EVM execution environments to provide comprehensive transaction volume measurement.

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

Confirmed transactions added to the blockchain.

Invarch

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown