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

## 1. Overview

Transaction count measures the total number of unique transactions executed on the Immutable zkEVM blockchain per day. This metric provides insight into network activity and adoption by counting distinct transaction hashes within daily time boundaries. The calculation ensures no duplicate transactions are counted while maintaining consistent daily aggregation across the blockchain.

## 2. Data sources

- **Blockchain transaction records**: Raw Immutable zkEVM transaction data containing transaction hashes, block timestamps, sender and receiver addresses
- **Transaction metadata**: Block numbers, gas usage metrics, and effective gas prices from transaction receipts
- **Chain configuration data**: Immutable-specific classification metadata and the hardcoded IMX token address (`0xf57e7e7c23978c3caec3c3548e3d615c346e79ff`)

## 3. Step-by-step calculation

### Component A: Transaction data standardization
- **Purpose**: Clean and standardize raw Immutable zkEVM transaction data for downstream processing
- **Logic**: Raw transaction records are extracted and key fields are cast to appropriate data types. The `block_timestamp` is converted to timestamp format, `block_number` to integer, `transaction_hash` to string, and address fields to string format. A hardcoded IMX token address is assigned to all transactions. Gas usage data is extracted from transaction receipts, with `receipt_gas_used` converted to bignumeric and `receipt_effective_gas_price` divided by 10^18 to convert from wei to ETH units.
- **Key fields**: `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, `gas_used`, `effective_gas_price`, and the assigned `token_address`

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day and apply proper classification metadata
- **Logic**: Transactions are grouped by truncating the `block_timestamp` to day-level granularity using timestamp truncation. For each day, distinct `transaction_hash` values are counted to ensure no duplicate transactions are included. Each record is classified with standardized metadata: `chain_id` as 'Immutable zkEVM', `product_id` as 'Immutable zkEVM', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'. The `to_address` field is preserved for potential contract-level analysis. Incremental processing logic ensures only recent data is reprocessed based on configurable lookback days.
- **Key fields**: Daily `timestamp`, `timestamp_grain` set to 'day', classification metadata fields, `to_address`, and the calculated `transaction_count`

### Final aggregation
- **Combining components**: The daily aggregated transaction counts are processed through the `finalize_metric_transaction_count` macro which applies standardized formatting and fills zero values for any missing days to ensure complete daily coverage
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: All timestamps are truncated to day-level granularity, with each day representing a complete 24-hour period in the blockchain's timezone
- **Final calculation**: The final metric value represents the count of distinct transaction hashes executed on Immutable zkEVM for each day, with chain availability filtering applied to ensure only data from active/supported chains is included in the final output

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

Confirmed transactions added to the blockchain.

ImmutableIMX

Transaction count

Transaction count

Competitive landscape

Chain breakdown