Tempo is a Layer 1 blockchain purpose-built for global payments, developed in partnership with leading fintechs and Fortune 500 companies and incubated by Stripe and Paradigm. It delivers high-throughput, low-cost global transactions with sub-second finality, predictable fees, and native stablecoin support.

website

twitter

Blockchains (L1)

Tempo

# Tempo Transactions per second Methodology

## 1. Overview

Transactions per second measures the average number of confirmed user transactions added to the Tempo blockchain each second. This metric reflects both the network’s throughput and real-time usage. By normalizing transaction volume over a standard time interval, the relative activity levels and capacity utilization of the network are quantified.

## 2. Data sources

- **Blockchain events**: transactions from Tempo
- **Transaction count**: Derived from the Transaction count metric

## 3. Step-by-step calculation

### Component A: Transaction filtering and extraction

- **Purpose**: Identifies and extracts successful transactions from the Tempo ledger
- **Logic**: Successful transactions are parsed from the Tempo ledger. Transactions are filtered to include only those with a successful receipt status, ensuring that failed executions do not inflate throughput metrics. A distinction is made between standard transactions and Multi-Payment Partition (MPP) transactions; while MPP transactions are unnested to identify individual calls for downstream analysis, the unique transaction hash is preserved for the primary count.
- **Key fields**: `transaction_hash` (unique identification), `receipt_status` (success verification), `transaction_type` (type classification)

### Component B: Daily transaction aggregation

- **Purpose**: Aggregates the total volume of network activity on a daily basis
- **Logic**: The total number of unique confirmed transactions is aggregated for each UTC day. This is calculated by performing a distinct count of transaction hashes to ensure that each user-initiated action is counted only once, regardless of the number of internal calls or partitions.
- **Key fields**: `block_timestamp` (timing), `transaction_hash` (unique identification)

### Component C: Throughput calculation

- **Purpose**: Normalizes daily transaction volume into a per-second frequency
- **Logic**: The average throughput is determined by dividing the total daily transaction count by the number of seconds in a day (86,400). The final transactions per second value is derived from this division, representing the average rate of transaction confirmation over a 24-hour period.
- **Key fields**: `transaction_count` (daily total)

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

Average confirmed user transactions added per second.

Tempo

Transactions per second

Transactions per second

Competitive landscape