Mode Network batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Mode Network is an L2 smart contract platform for decentralized applications on Ethereum. Mode Network was founded by James Ross and launched in 2024.

Mode Network team & investors own and govern the protocol. Mode Network has received a $6 million grant from the Optimism Foundation.

github

twitter

discord

website

Blockchains (L2)

Mode Network

# Mode Network Transaction count Methodology

## 1. Overview

Transaction count measures the total number of unique transactions processed on the Mode blockchain each day. This metric provides insight into network activity and user engagement by counting distinct transaction hashes per day. The calculation aggregates raw blockchain transaction data on daily boundaries and ensures data completeness through gap-filling and validation processes.

## 2. Data sources

- **Mode blockchain transaction records**: Complete transaction history from the Mode L2 blockchain, including transaction hashes, sender addresses, recipient addresses, block timestamps, and block-level metadata
- **Chain availability configuration**: Metadata defining valid time periods when Mode blockchain data should be included in calculations

## 3. Step-by-step calculation

### Component A: Transaction data standardization
- **Purpose**: Standardize raw Mode transaction data and prepare it for aggregation
- **Logic**: Raw transaction records from Mode blockchain are processed with basic field casting to ensure consistent data types. Each transaction record includes the `block_timestamp`, `transaction_hash`, `from_address`, and `to_address` fields. All transactions are labeled with chain identifier 'mode' for downstream processing.
- **Key fields**: `block_timestamp` (when transaction was included in block), `transaction_hash` (unique transaction identifier), `from_address` (transaction sender), `to_address` (transaction recipient)

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day and apply business metadata
- **Logic**: Standardized transaction data is aggregated using daily time boundaries created by truncating `block_timestamp` to day level. For each day and `to_address` combination, unique transactions are counted using distinct `transaction_hash` values to avoid double-counting. Business metadata is applied including chain identifier ('mode'), market sector ('blockchains_l2'), and business segment ('blockchain'). Product and contract name fields are set to null as this is a chain-level metric.
- **Key fields**: `timestamp` (day-level boundary), `transaction_count` (distinct count of transactions), `to_address` (recipient address for grouping)

### Final aggregation
- **Combining components**: Daily aggregated data flows through the finalize metric macro which applies schema validation, ensures proper field formats, and validates business identifiers
- **Currency conversion**: Not applicable for transaction count metric
- **Time aggregation**: Daily boundaries are maintained with gap-filling logic that inserts zero values for any missing days to ensure complete time series continuity
- **Final calculation**: The final metric represents the count of unique transactions per day on Mode blockchain, with each day showing the total number of distinct `transaction_hash` values that occurred within that 24-hour period, grouped by recipient address and aggregated across all Mode network activity

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

Confirmed transactions added to the blockchain.

Mode NetworkMODE

Transaction count

Transaction count

Competitive landscape

Chain breakdown