twitter

etherscan

website

Blockchains (L2)

Unichain

# Unichain Transactions per second Methodology

## 1. Overview

The transactions per second (TPS) metric measures the average number of transactions processed per second on the Unichain blockchain over a daily period. This metric provides insight into network throughput and usage by calculating the daily transaction volume divided by the number of seconds in a day (86,400). The calculation uses an approximate distinct count approach to handle potential duplicate transaction records and employs incremental processing for efficient data updates.

## 2. Data sources

- **Unichain transaction records**: Complete transaction data from the Unichain blockchain including block timestamps, transaction hashes, sender and recipient addresses, and gas usage information
- **Table edit cache**: Metadata tracking the last modification times of processed partitions to enable efficient incremental data processing

## 3. Step-by-step calculation

### Component A: Raw transaction data extraction
- **Purpose**: Extract and standardize transaction records from the Unichain blockchain
- **Logic**: Select relevant transaction fields from Unichain blockchain data and cast them to appropriate data types. Each record includes the block timestamp when the transaction was processed, unique transaction hash identifier, sender (`from_address`) and recipient (`to_address`) addresses, plus gas usage metrics. Fixed values are assigned including token address for ETH (`0x4200000000000000000000000000000000000006`), token symbol (`ETH`), and chain identifier (`unichain`)
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction participants, and gas-related fields for fee calculations

### Component B: Daily transaction aggregation  
- **Purpose**: Count distinct transactions per day grouped by destination address
- **Logic**: Aggregate transaction records by truncating `block_timestamp` to daily boundaries and group by destination address (`to_address`). Use approximate distinct count of `transaction_hash` values to calculate total transactions while handling potential duplicates efficiently. Apply fixed categorical assignments including chain identifier (`unichain`), market sector (`blockchains_l2`), and business segment (`blockchain`). For incremental processing, filter to only include transactions from recent partitions based on the table edit cache
- **Key fields**: Daily `timestamp` boundary, `transaction_count` from approximate distinct counting, `chain_id` for blockchain identification, and `to_address` for recipient-level grouping

### Final aggregation
- **Combining components**: Sum the daily transaction counts across all destination addresses to get total daily transaction volume for the Unichain network
- **Currency conversion**: Not applicable - this metric measures transaction count, not monetary values
- **Time aggregation**: Data is aggregated to daily granularity by truncating block timestamps to day boundaries
- **Final calculation**: Divide the total daily transaction count by the number of seconds in a day (86,400) using safe division to prevent division by zero errors. The result represents the average transactions per second for each day. Missing days in the time series are filled with zero values to maintain continuity in the metric series

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

Average confirmed user transactions added per second.

UnichainUNI

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown