Immutable operates a full-stack infrastructure platform for web3 gaming that includes blockchains, namely Immutable zkEVM and Immutable X, and other products, such as Passport and Orderbook. Creators & users sell NFTs on Immutable. They receive royalties from secondary sales (supply-side fees).

Immutable is a platform for building web3 games. Immutable was founded by James Ferguson, Robbie Ferguson, Alex Connolly, and launched in 2018. This dashboard includes data from Immutable Orderbook, Immutable zkEVM, and Immutable X.

IMX holders own and govern the protocol. They currently take a cut of the total trading fees paid by NFT buyers on Immutable Orderbook and the total transaction fees paid by transaction senders on Immutable zkEVM (revenue). Immutable's investors include ParaFi Capital, GameStop Digital Ventures, Fabric Ventures, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L2)

Immutable

# Immutable Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the Immutable X zkEVM blockchain per second on a daily basis. This metric provides insight into network throughput and activity levels by calculating the daily transaction volume divided by the number of seconds in a day (86,400). The calculation tracks all transaction types on the Immutable X zkEVM network and represents the sustained transaction processing capacity of the blockchain.

## 2. Data sources

- **Immutable X zkEVM transaction records**: Complete transaction data from the Immutable X zkEVM blockchain including transaction hashes, block timestamps, sender and receiver addresses, gas usage metrics, and transaction status information
- **Chain availability configuration**: Data availability periods and operational status information for the Immutable X zkEVM network to ensure accurate metric calculation during periods of complete data coverage

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw transaction data from the Immutable X zkEVM blockchain
- **Logic**: Retrieves all transaction records from Immutable X zkEVM blockchain data, extracting key fields including `block_timestamp`, `block_number`, `transaction_hash`, `from_address`, `to_address`, `gas_used`, and `effective_gas_price`. The data is cast to appropriate types with timestamp conversion and gas price normalization by dividing by 10^18 to convert from wei to ETH units. A hardcoded IMX token address `0xf57e7e7c23978c3caec3c3548e3d615c346e79ff` is assigned as the primary token identifier.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction parties, `gas_used` and `effective_gas_price` for cost metrics

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day grouped by destination address
- **Logic**: Aggregates transaction data by truncating `block_timestamp` to daily granularity and counting distinct `transaction_hash` values. Groups results by day, chain identifier, market sector, business segment, product identifier, and `to_address`. Includes metadata classification with chain as "Immutable zkEVM", market sector as "blockchains_l2", business segment as "blockchain", and product as "Immutable zkEVM". Uses incremental processing with lookback periods to efficiently update only recent data.
- **Key fields**: `timestamp` (daily), `transaction_count` (distinct count), `to_address` for recipient grouping, classification fields for categorization

### Component C: Transactions per second calculation  
- **Purpose**: Convert daily transaction counts to average transactions per second
- **Logic**: Takes the daily transaction count aggregation and divides the sum of `transaction_count` by a predefined variable representing seconds in a day (86,400 seconds). Groups by `timestamp`, `timestamp_grain`, `product_id`, and `chain_id` to calculate TPS at the daily level for the entire network. Uses safe division to handle potential zero denominators.
- **Key fields**: `transactions_per_second` as the calculated rate, daily grouping fields for aggregation level

### Final aggregation
- **Combining components**: The calculation flows sequentially from raw transactions to daily counts to TPS calculation, with each component feeding into the next
- **Currency conversion**: No currency conversion required as this is a volume metric measured in transactions per second
- **Time aggregation**: All calculations use daily time boundaries with timestamp truncation to day granularity, providing daily average TPS values
- **Final calculation**: Transactions per second equals the total daily transaction count divided by 86,400 seconds, representing the average sustained transaction processing rate for each day. The result includes metric finalization with gap filling using zeros for missing periods and chain availability filtering to exclude periods with incomplete data coverage.

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

Average confirmed user transactions added per second.

ImmutableIMX

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown