website

github

twitter

discord

Blockchains (L3)

ApeChain

# Transactions per second Methodology

## Overview

Transactions per second measures the average number of confirmed user transactions added to the blockchain each second. It reflects both the network’s throughput and real-time usage.

## Data sources

- Blockchain transaction records including hashes and status
- Block metadata capturing timestamps and confirmational data
- Network performance monitoring feeds and message logs

## Common calculation approaches

### Transaction count normalization
Raw transaction counts are extracted from blockchain records and normalized by the total number of seconds in a day (86,400). For example, unique transactions are aggregated from block metadata on networks such as Base and Tron to determine average daily throughput.

### Network-level performance tracking
For high-throughput environments, transaction rates are derived from pre-aggregated network statistics or instruction execution data. Message execution data is extracted from Internet Computer, while confirmed transaction counts are processed from block metadata and program instructions on Solana.

### Cross-layer ecosystem aggregation
Network activity is consolidated across multiple layers to represent the total throughput of an ecosystem. Transaction counts are aggregated from BNB Chain—including both the BSC Layer 1 and the opBNB Layer 2—and divided by the daily time interval to calculate a combined rate.

**Note:** The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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

Average confirmed user transactions added per second.

ApeChainAPE

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown