Validators process transactions and receive fees from users (supply-side fees).

Celo is a smart contract platform for decentralized applications (a blockchain). Celo was founded by Rene Reinsberg and Marek Olszewski and launched in 2020.

CELO holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Celo's investors include a16z, Greenfield, Electric Capital, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L2)

Celo

# Celo Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the Celo L1 (legacy) blockchain per second on a daily basis. This metric provides insight into network throughput and usage intensity. The calculation divides the total number of unique transactions in a day by 86,400 seconds, providing a daily average TPS figure. The methodology accounts for Celo L1 (legacy)'s network transition from L1 to L2 operations that occurred on March 26, 2025.

## 2. Data sources

The calculation relies on the following data sources:

- **Celo L1 (legacy) blockchain transaction records**: Raw transaction data from the Celo L1 (legacy) blockchain including transaction hashes, block timestamps, sender and recipient addresses, gas usage, and fee information
- **End-of-day price feeds**: Token Terminal's standardized price feeds for currency conversion (used implicitly in finalization macros)
- **Token Terminal configuration data**: Internal configuration for metric standardization, chain availability filters, and schema validation

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw Celo L1 (legacy) blockchain transaction data
- **Logic**: Raw Celo L1 (legacy) transaction records are extracted and cast to appropriate data types. Key fields include `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, gas information, and fee currency. The fee currency defaults to Celo L1 (legacy)'s native token address (`0x471ece3750da237f93b8e339c536989b8978a438`) when not specified. Gas prices are normalized by dividing by 10^18 to convert from wei to standard units.
- **Key fields**: `block_timestamp` (transaction timing), `transaction_hash` (unique identifier), `from_address` and `to_address` (transaction parties), `gas_used` and `effective_gas_price` (execution costs)

### Component B: Temporal classification and transaction counting
- **Purpose**: Classify transactions by network type and aggregate daily counts
- **Logic**: Transactions are classified based on a temporal cutoff at March 26, 2025. Transactions before this date are tagged as Celo L1 (legacy) L1 operations with `product_id` of 'Celo L1 (legacy)' and `market_sector_id` of 'blockchains_l1'. Transactions from March 26, 2025 onward are classified as Celo L1 (legacy) L2 operations with `product_id` of 'Celo L1 (legacy) L2' and `market_sector_id` of 'blockchains_l2'. For each classification, transactions are aggregated daily by truncating `block_timestamp` to day boundaries and counting distinct `transaction_hash` values to avoid double-counting.
- **Key fields**: `timestamp` (daily boundary), `product_id` ('Celo L1 (legacy)' or 'Celo L1 (legacy) L2'), `market_sector_id` ('blockchains_l1' or 'blockchains_l2'), `transaction_count` (distinct daily transactions)

### Component C: Transactions per second calculation
- **Purpose**: Convert daily transaction counts to average transactions per second
- **Logic**: The daily transaction count for each classification is divided by the number of seconds in a day (86,400) using a safe division operation. This creates an average TPS figure that represents the sustained transaction rate if transactions were evenly distributed throughout the day.
- **Key fields**: `transactions_per_second` (daily transaction count ÷ 86,400)

### Final aggregation
- **Combining components**: The TPS calculations for both Celo L1 (legacy) L1 and L2 are combined, maintaining separate product classifications to track the network transition
- **Currency conversion**: Not directly applicable to transaction count metrics, but standardization macros ensure consistent formatting
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a single TPS measurement
- **Final calculation**: The final TPS value equals the total number of unique transactions in a day divided by 86,400 seconds, providing the average transactions per second for that day

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

Average confirmed user transactions added per second.

CeloCELO

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown