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

## 1. Overview

The Aptos transaction count metric measures the daily number of unique transactions executed on the Aptos blockchain. This metric provides insight into network activity and user engagement by counting distinct transaction hashes per day. The calculation includes special handling for genesis transactions and applies data quality validation to ensure complete daily time series coverage.

## 2. Data sources

- **Aptos blockchain transaction records**: Raw transaction data from the Aptos network containing transaction hashes, timestamps, sender addresses, gas usage, and gas pricing information
- **Genesis transaction handling**: Special processing for pre-mainnet transactions with hardcoded mainnet launch timestamp of October 12th, 2022

## 3. Step-by-step calculation

### Component A: Transaction fact preparation
- **Purpose**: Processes raw Aptos transaction data and handles genesis transactions
- **Logic**: Extracts all transaction records from the Aptos blockchain including `hash`, `sender`, `block_timestamp`, `gas_used`, and `gas_unit_price` fields. Applies special handling for genesis transactions by identifying any transactions with timestamps before January 1st, 2000 and reassigning them to the mainnet launch date of October 12th, 2022. The `gas_unit_price` is converted from its raw form by dividing by 10^8 to account for decimal precision. All other transactions retain their original timestamps if after January 1st, 2000.
- **Key fields**: `transaction_hash` (unique identifier), `block_timestamp` (transaction timing), `sender` (transaction originator), `gas_used` (computational cost), `gas_unit_price` (price per gas unit in adjusted decimals)

### Component B: Daily transaction aggregation
- **Purpose**: Aggregates transactions into daily counts with metadata classification
- **Logic**: Groups transactions by day using timestamp truncation to daily boundaries. Counts distinct transaction hashes for each day to ensure unique transactions are measured. Adds standardized metadata fields including `chain_id` set to 'aptos', `market_sector_id` set to 'blockchains_l1', `business_segment_id` set to 'blockchain', and `product_id` set to null. For incremental processing, only processes transactions from the maximum partition date minus a configurable lookback period to handle late-arriving data.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct hash count), classification metadata fields

### Final aggregation
- **Combining components**: The daily aggregated transaction counts flow directly into the finalization process without additional joining
- **Metric finalization**: Applies schema validation, ID validation, and gap-filling using a 'fill_zeros' strategy to ensure complete daily coverage with zero values for days without transactions
- **Chain availability filtering**: Applies final filtering based on chain availability configuration to exclude data outside of supported time periods
- **Final calculation**: The metric represents the count of distinct transaction hashes per day on the Aptos blockchain, with special genesis handling and complete time series validation

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

Confirmed transactions added to the blockchain.

AptosAPT

Transaction count

Transaction count

Competitive landscape