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

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the IoTeX blockchain per second on a daily basis. This metric provides insight into network throughput and usage patterns by calculating the daily transaction volume divided by the number of seconds in a day (86,400). The calculation aggregates all unique transactions on the IoTeX blockchain and converts the daily count to an average per-second rate.

## 2. Data sources

- **IoTeX blockchain transaction records**: Raw transaction data from the IoTeX blockchain including transaction hashes, block timestamps, sender and recipient addresses, and gas usage information
- **IoTeX block data**: Block-level information including block numbers and timestamps for temporal organization and EIP-1559 activation tracking
- **Gas pricing data**: Transaction gas prices and effective gas prices, with special handling for the EIP-1559 activation at block 33730921 (Vanuatu upgrade)

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Clean and standardize raw IoTeX transaction data for analysis
- **Logic**: Extract all IoTeX blockchain transactions and apply data cleaning transformations. Normalize addresses to lowercase format for consistency. Handle gas pricing with protocol-specific logic where pre-EIP-1559 transactions (before block 33730921) use `gas_price` field, while post-EIP-1559 transactions use `receipt_effective_gas_price`. Convert gas prices from wei to IOTX by dividing by 10^18. Include additional metadata like market sector (`blockchains_l1`) and business segment (`blockchain`) classifications.
- **Key fields**: `transaction_hash` for unique identification, `block_timestamp` for temporal analysis, `from_address` and `to_address` for transaction participants, `gas_used` and `effective_gas_price` for fee calculations

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day to establish daily transaction volume
- **Logic**: Group processed transaction data by day using timestamp truncation to daily boundaries. Count distinct transaction hashes within each day to ensure no double-counting of transactions. Group results by timestamp, chain identifier, market sector, business segment, and destination address. This creates a comprehensive daily transaction count dataset that captures the total unique transaction volume for each day.
- **Key fields**: `timestamp` truncated to day level, `transaction_count` as distinct count of `transaction_hash`, `chain_id` set to 'iotex', `to_address` for transaction destination tracking

### Final aggregation
- **Combining components**: The daily transaction counts are processed through the TPS calculation logic where the `transaction_count` field from the daily aggregation is used as input
- **Currency conversion**: No currency conversion required as this is a transaction volume metric, not a monetary value
- **Time aggregation**: Daily boundaries are maintained with timestamp truncation to day level, ensuring consistent 24-hour periods for TPS calculations
- **Final calculation**: Divide the sum of daily transaction counts by the number of seconds in a day (86,400) using safe division to handle edge cases. The formula is: `safe_divide(sum(transaction_count), 86400)` which produces the average transactions per second for each day. Data validation and gap-filling are applied through finalize metric macros to ensure data quality and completeness.

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

Average confirmed user transactions added per second.

IoTeXIOTX

Archived

Transactions per second

Transactions per second

Competitive landscape