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

Kusama is a security & interoperability platform for blockchains and applications. Kusama was founded by Gavin Wood and launched in 2019.

KSM holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue).

github

twitter

discord

etherscan

website

Blockchains (L1)

Kusama

# Kusama Transactions per second Methodology

## 1. Overview

Transactions per second measures the average daily transaction throughput on the Kusama network. This metric answers the question "How many transactions does Kusama process per second on average?" by calculating the daily transaction volume and dividing by the number of seconds in a day (86,400). The metric provides insight into network utilization and processing capacity.

## 2. Data sources

- **Kusama blockchain extrinsic records**: Raw transaction data from the Kusama blockchain, where each extrinsic represents a transaction or state change operation
- **Daily time dimension data**: Time boundaries for daily aggregation and gap-filling logic
- **Chain availability configuration**: Filters to exclude periods when the chain was inactive or data unavailable

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize raw Kusama transaction data
- **Logic**: Retrieve all extrinsic records from Kusama blockchain data, casting `block_timestamp` to proper timestamp format and `extrinsic_id` to string format. Each extrinsic represents a transaction on the Kusama network. The data is tagged with `chain_id` as 'kusama' for identification.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `extrinsic_id` (unique identifier for each transaction), `chain_id` (always 'kusama')

### Component B: Daily transaction count aggregation
- **Purpose**: Count unique transactions per day to establish daily throughput
- **Logic**: Group all transactions by day using timestamp truncation to daily boundaries. Count distinct `extrinsic_id` values to avoid double-counting any transactions. Apply incremental processing to only recalculate recent days when updating the data. Tag each day with metadata including market sector as 'blockchains_l2', business segment as 'blockchain', and set `product_id` to null since this is chain-level data.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` ('day'), `chain_id` ('kusama'), `transaction_count` (distinct daily transaction count)

### Final aggregation
- **Combining components**: The daily transaction counts flow directly into the final calculation without additional joining
- **Currency conversion**: No currency conversion needed as this is a count-based metric
- **Time aggregation**: Data is aggregated at daily boundaries, with gap-filling logic ensuring continuous daily records
- **Final calculation**: Divide the daily transaction count by 86,400 (seconds in a day) using safe division to handle any potential zero values. This converts absolute daily transaction counts into an average transactions-per-second rate for each day. Apply chain availability filters to exclude periods when the Kusama network was inactive or when data was unavailable. Fill any missing days with zero values to maintain continuous time series data.

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

Average confirmed user transactions added per second.

KusamaKSM

Transactions per second

Transactions per second

Competitive landscape