Node operators process transactions and receive token incentives. These independently owned high-spec node machines around the world are connected via Internet Computer Protocol (ICP), creating a self-sovereign network not reliant on any cloud services. Advanced cryptography allows any application or service to be run on the network in a decentralized manner via smart contracts.

The Internet Computer is a decentralized cloud blockchain, where apps can be built fully onchain, using AI, or by coding. Try caffeine.ai & icp.ninja.

ICP tokenholders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). ICP Holders can stake their ICP on the Network Nervous System (NNS), an advanced fully on-chain DAO that facilitates liquid democracy. Staking ICP allows users to submit proposals, vote on proposals, and earn rewards for their participation in governance. Internet Computer's investors include Polychain, Scalar Capital, Amino Capital, etc.

github

twitter

discord

website

Blockchains (L1)

Internet Computer

# Internet Computer Transaction count Methodology

## 1. Overview

The Internet Computer transaction count metric measures the total number of transactions processed daily on the Internet Computer blockchain. Unlike traditional blockchains where transaction counts are derived from block-by-block analysis, this metric is calculated by converting pre-aggregated average transactions per second statistics into daily totals. The calculation multiplies the daily average transactions per second by 86,400 (the number of seconds in a day) to estimate total daily transaction volume.

## 2. Data sources

The calculation relies on:
- **Network statistics API**: Scraped data from Internet Computer's official network statistics or dashboard containing daily aggregated metrics
- **Daily performance metrics**: Pre-calculated average transactions per second values for each day from the Internet Computer foundation's monitoring systems
- **Blockchain metadata**: Timestamp and chain identification information embedded in the scraped statistics

## 3. Step-by-step calculation

### Component A: Raw data extraction
- **Purpose**: Extract daily average transaction rates from scraped Internet Computer network statistics
- **Logic**: The system processes JSON-formatted data from Internet Computer's statistics API that contains nested daily statistics arrays. For each day, it extracts the `day` timestamp and `average_transactions_per_second` value from the JSON structure. The data parsing handles nested JSON arrays where daily statistics are stored within a broader statistics payload.
- **Key fields**: `timestamp` (parsed from day field), `average_transactions_per_second` (the core rate metric), and `inserted_at` (when the data was scraped)

### Component B: Data deduplication
- **Purpose**: Ensure only the most recent data is used when multiple scraping runs exist for the same day
- **Logic**: Since the scraper may collect data multiple times for the same day, the system applies deduplication logic by ranking each day's records based on their insertion timestamp. It uses row numbering partitioned by the daily timestamp and ordered by insertion time to identify the most recently scraped data. Only records with row number 1 (most recent) are retained for further processing.
- **Key fields**: `row_number` (ranking based on insertion time), deduplicated `timestamp`, `chain`, and `amount` fields

### Final aggregation
- **Combining components**: The deduplicated average transactions per second data flows directly into the final calculation without additional joins, as the Internet Computer provides pre-aggregated statistics rather than raw transaction events
- **Currency conversion**: Not applicable - transaction counts are unitless metrics
- **Time aggregation**: Data is already aggregated daily at the source level, with each record representing a full day's average transaction rate
- **Final calculation**: The daily transaction count is calculated by multiplying the average transactions per second by 86,400 (seconds per day). For example, if the average transactions per second is 10.5, the daily total would be 10.5 × 86,400 = 907,200 transactions. The system applies standard metric finalization including schema validation, gap filling with zeros for missing days, and chain availability filtering to ensure data quality and consistency.

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

Confirmed transactions added to the blockchain.

Internet ComputerICP

Transaction count

Transaction count

Competitive landscape