IoTeX is the blockchain platform for Real-World AI. Since 2017, its foundational infrastructure has delivered verified, real-time data from the real world to AI systems and decentralized applications. Powering 100+ projects and 40M devices across mobility, robotics, energy, health, and more, IoTeX enables developers to build next-gen AI models and applications that deliver real-world impact. The IoTeX tech stack provides the data, identity, and verification layers to fulfill the surging demand for real-world data in the new AI era. Trusted by partners like Google, Samsung, IEEE, ARM, and Nordic Semiconductor, IoTeX is uniquely positioned to capture the multi-trillion-dollar AI and data economy.

website

twitter

github

discord

Blockchains (L1)

IoTeX

# IoTeX Transaction count Methodology

## 1. Overview

The IoTeX transaction count metric measures the daily number of unique transactions executed on the IoTeX blockchain. This metric provides insight into network activity and adoption by counting each distinct transaction that occurred on any given day. The calculation aggregates raw blockchain transaction data to produce daily transaction counts, with special handling for IoTeX's network upgrades and gas pricing mechanisms.

## 2. Data sources

- **IoTeX blockchain transaction records**: Raw transaction data from the IoTeX network containing transaction hashes, block information, sender/recipient addresses, gas usage, and pricing details
- **IoTeX block data**: Block timestamps and block numbers used for temporal aggregation and network upgrade logic
- **Table modification cache**: Internal system data used to optimize incremental data processing and track the last update timestamp

## 3. Step-by-step calculation

### Component A: Raw transaction processing
- **Purpose**: Extract and standardize raw IoTeX transaction data with proper gas pricing calculations
- **Logic**: The system processes raw IoTeX blockchain transaction records, extracting key fields including `transaction_hash`, `block_timestamp`, `block_number`, `from_address`, `to_address`, and gas-related fields. Address values are converted to lowercase for consistency. The model applies IoTeX-specific business logic for gas pricing that accounts for the network's EIP-1559 activation at block 33730921 (Vanuatu upgrade). For transactions before this block, gas pricing uses the `gas_price` field, while transactions after use the `receipt_effective_gas_price` field. Gas prices are converted from wei to IOTX by dividing by 10^18. The system also processes incremental updates by filtering to recent data based on the last partition timestamp plus a configurable lookback period.
- **Key fields**: `transaction_hash` for unique transaction identification, `block_timestamp` for temporal grouping, `from_address` and `to_address` for transaction participants, `gas_used` and gas pricing fields for fee calculations

### Component B: Daily aggregation
- **Purpose**: Group transactions by day and calculate daily transaction counts
- **Logic**: The processed transaction data is aggregated to daily granularity using timestamp truncation to day boundaries. The system counts distinct transaction hashes grouped by day and recipient address (`to_address`), ensuring each unique transaction is counted exactly once per day. Metadata fields are added including `chain_id` set to 'iotex', `market_sector_id` set to 'blockchains_l1', and `business_segment_id` set to 'blockchain'. The `product_id` field is set to null as this represents overall network activity rather than a specific product.
- **Key fields**: `timestamp` truncated to day, `transaction_count` as distinct count of `transaction_hash`, `to_address` for recipient-level grouping

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that standardizes the output schema, validates identifier fields, and ensures no gaps exist in the time series data using a 'fill_zeros' strategy
- **Currency conversion**: Not applicable as this metric counts transactions rather than measuring monetary values
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a complete 24-hour period in the blockchain's native timezone
- **Final calculation**: The final metric value represents the total number of distinct transactions that occurred on the IoTeX network for each day, with a chain availability filter applied to ensure data quality and completeness

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

Confirmed transactions added to the blockchain.

IoTeXIOTX

Archived

Transaction count

Transaction count

Competitive landscape