website

github

twitter

discord

Blockchains (L3)

ApeChain

# Transaction count Methodology

## Overview

Transaction count measures the number of confirmed transactions added to the blockchain. It reflects how actively users engage with the network.

## Data sources

- Raw blockchain transaction records and unique transaction hashes
- Block metadata and ledger headers
- Network performance APIs and daily monitoring statistics

## Common calculation approaches

### Transaction hash aggregation
Unique transaction hashes are aggregated daily from raw blockchain records to quantify network activity. For blockchains such as BNB Chain and Base, distinct hashes are counted from both Layer 1 and Layer 2 environments to provide a comprehensive view of transaction activity across the ecosystem.

### Block metadata extraction
Transaction totals are retrieved directly from block headers or ledger metadata. For example, on Solana, the `total_transaction_count` is extracted from block-level data to include all confirmed interactions, including asset transfers and program instructions. Similarly, transaction counts are derived from ledger records on the Stellar network.

### Statistical performance conversion
Daily totals are derived from high-frequency network performance metrics when direct hash counts are not the primary data source. On the Internet Computer, daily transaction counts are calculated by converting average transactions per second (TPS) statistics into 24-hour totals.

**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.*

Confirmed transactions added to the blockchain.

ApeChainAPE

Transaction count

Transaction count

Competitive landscape

Chain breakdown