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

Cosmos Hub is an interoperability & security platform for blockchains and applications. Cosmos was founded by Ethan Buchman & Jae Kwon and launched in 2019.

ATOM holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Cosmos’s investors include Paradigm, IOSG Ventures, 1confirmation, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

Cosmos Hub

# Cosmos Hub Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Cosmos Hub blockchain over a daily period. 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 uses a straightforward approach: count all unique transactions per day, then divide by the total seconds in that day to derive the average transactions per second.

## 2. Data sources

- **Blockchain transaction data**: Raw Cosmos Hub transaction records containing block timestamps, transaction hashes, and transaction fee information
- **Chain availability data**: Configuration data used to filter and validate chain availability for data quality assurance

## 3. Step-by-step calculation

### Component A: Transaction data processing
- **Purpose**: Processes raw Cosmos Hub transaction data and standardizes transaction fees
- **Logic**: Extracts all transactions from Cosmos Hub blockchain data, focusing on core transaction identifiers and timing. Transaction fees are converted from their native microatom denomination to atom units by dividing by 10^6 (1,000,000). Each transaction is identified by its unique `transaction_hash` and timestamped with its `block_timestamp`. The fee unit is standardized as `uatom` for consistency across the dataset.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for unique transaction identification, `transaction_fee` converted to atom units

### Component B: Daily transaction aggregation
- **Purpose**: Aggregates transaction data to daily granularity and counts unique transactions
- **Logic**: Groups all processed transactions by day using timestamp truncation to daily boundaries. For each day, counts the number of distinct transaction hashes to determine the total daily transaction volume. This approach ensures duplicate transactions (if any) are not double-counted. The aggregation also assigns standard metadata including chain identifier as `cosmos`, market sector as `blockchains_l1`, and business segment as `blockchain`.
- **Key fields**: `timestamp` truncated to day, `transaction_count` as distinct hash count, chain and sector classification fields

### Final aggregation
- **Combining components**: The daily transaction counts flow directly from the aggregation component to the TPS calculation
- **TPS conversion**: Divides the daily transaction count by 86,400 (the number of seconds in a day) using safe division to prevent errors from potential zero values
- **Time aggregation**: Maintains daily granularity with each day's TPS representing the average transactions per second for that 24-hour period  
- **Final calculation**: The final TPS value equals daily transaction count divided by seconds per day, with gap filling applied to insert zero values for days with no transaction activity, and chain availability filters applied to ensure data quality and completeness

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

Average confirmed user transactions added per second.

Cosmos HubATOM

Transactions per second

Transactions per second

Competitive landscape