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

Aptos is a smart contract platform for decentralized applications (a blockchain). Aptos was founded by Mo Shaikh and Avery Ching and launched in 2022.

APT token holders own and govern the protocol. They currently don’t take a cut of the total transaction fees paid by users (revenue). Aptos’ investors include Binance Labs, Jump Crypto, Apollo, etc.

governance

github

twitter

discord

website

Blockchains (L1)

Aptos

# Aptos Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average rate of transaction processing on the Aptos blockchain over a 24-hour period. This metric answers the business question of network throughput and capacity utilization by calculating how many unique transactions are processed per second on average each day. The calculation takes the total daily transaction count and divides by the number of seconds in a day (86,400) to produce a daily average TPS value.

## 2. Data sources

- **Aptos blockchain transaction records**: Complete transaction history including block timestamps, transaction hashes, sender addresses, gas usage, and gas unit prices
- **Chain availability configuration**: Data used to filter out periods when the Aptos blockchain was unavailable or experiencing issues

## 3. Step-by-step calculation

### Component A: Raw transaction extraction
- **Purpose**: Extract and normalize all Aptos blockchain transactions with special handling for genesis block data
- **Logic**: Pull all transaction records from Aptos blockchain data, including `block_timestamp`, transaction `hash`, `sender` address, `gas_used`, and `gas_unit_price`. Apply special handling for genesis block transactions by reassigning any transactions with timestamps before 2000-01-01 to the hardcoded genesis date of October 12, 2022 at 00:00:00 UTC. Normalize gas unit prices by dividing by 10^8 to account for Aptos decimal precision.
- **Key fields**: `block_timestamp` for daily grouping, `transaction_hash` for unique counting, `sender` for transaction attribution, and normalized gas pricing fields

### Component B: Daily transaction count aggregation  
- **Purpose**: Calculate the total number of unique transactions processed each day on the Aptos blockchain
- **Logic**: Group transaction records by day using timestamp truncation to daily boundaries. Count distinct transaction hashes within each day to ensure no double-counting of transactions. Assign standard metadata including 'aptos' as `chain_id`, 'blockchains_l1' as `market_sector_id`, 'blockchain' as `business_segment_id`, and null for `product_id`. Apply incremental processing logic to only recalculate recent periods when updating.
- **Key fields**: Daily `timestamp`, `transaction_count` as distinct count of hashes, and standardized classification fields

### Final aggregation
- **Combining components**: The daily transaction counts serve as the single input for the final TPS calculation
- **Rate conversion**: Divide each day's total transaction count by the number of seconds in a day (86,400 seconds) using safe division to handle potential null or zero values
- **Time aggregation**: Maintain daily grain with each day's TPS representing the average transactions per second for that 24-hour period  
- **Schema standardization**: Apply finalize metric macro to ensure consistent schema structure, validate metadata IDs, and fill any gaps in the time series with zero values
- **Availability filtering**: Apply chain availability filters to exclude data from periods when the Aptos blockchain was experiencing downtime or technical issues
- **Final calculation**: For each day, TPS = (total unique transactions in that day) ÷ (86,400 seconds) = average transactions per second for that day

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

Average confirmed user transactions added per second.

AptosAPT

Transactions per second

Transactions per second

Competitive landscape