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 Transaction count Methodology

## 1. Overview

The number of confirmed transactions added to the blockchain is measured by Transaction count. How actively users engage with the network is reflected by this metric. Both standard transactions and Multi-Purpose Payment (MPP) transactions are included so that a comprehensive view of successful on-chain interactions is provided.

## 2. Data sources

- **Blockchain events**: Transaction records from the Tempo network, covering Tempo

## 3. Step-by-step calculation

### Component A: Tempo transaction filtering

- **Purpose**: The identification and filtering of successful transactions
- **Logic**: Transactions are filtered so that only those with a successful receipt status are included. Transactions are categorized by type, where type 118 is identified as a Multi-Purpose Payment (MPP) and other types are treated as standard transactions. Failed transactions are excluded from the count.
- **Key fields**: `receipt_status`, `transaction_type`

### Component B: Multi-Purpose Payment (MPP) processing

- **Purpose**: The processing of complex transaction structures
- **Logic**: For transactions classified as MPP, the internal `calls` array is unnested for the identification of destination addresses. This mapping is performed so that the correct processing of the transaction within the data pipeline is ensured while the unique transaction hash is preserved for counting.
- **Key fields**: `calls` array

### Component C: Final aggregation and deduplication

- **Purpose**: The calculation of daily totals and maintenance of data continuity
- **Logic**: The count of unique transaction hashes is aggregated at a daily granularity. Deduplication is performed so that each transaction is counted only once, even if multiple internal calls are present. The final values are grouped by UTC timestamps, and a zero-filling strategy is applied so that a continuous data sequence is maintained.
- **Key fields**: `transaction_hash`, `block_timestamp`

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

Confirmed transactions added to the blockchain.

Tempo

Transaction count

Transaction count

Competitive landscape