Validators process transactions and receive validator rewards (supply-side fees).

NEAR Protocol is a smart contract platform for decentralized applications (a blockchain). NEAR Protocol was founded by Alexander Skidanov & Ilya Polosukhin and launched in 2017.

NEAR holders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). NEAR Protocol's investors include a16z, Pantera Capital, Libertus, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

NEAR Protocol

# near Transaction Count Methodology

## 1. Overview

Transaction Count measures the total number of unique transactions successfully processed and recorded on Near Protocol. This metric serves as a primary indicator of network activity and user engagement within the Near Protocol ecosystem. Transactions are counted at the protocol level, representing the aggregate volume of all interactions, including asset transfers, contract calls, and account management operations.

## 2. Data sources

- **Blockchain events**: `transactions` data from Near Protocol ledger records, covering Near

## 3. Step-by-step calculation

### Component A: Transaction data extraction

- **Purpose**: Retrieve raw transaction records from the Near Protocol datalake.
- **Logic**: Transaction hashes, block timestamps, and account identifiers are extracted from the core transaction tables. Data points including gas burnt and tokens burnt are retrieved to validate transaction finality, while the `transaction_hash` is utilized as the unique identifier for each record.
- **Key fields**: `transaction_hash`, `block_timestamp`

### Component B: Unique transaction aggregation

- **Purpose**: Calculate the total volume of distinct transactions per day.
- **Logic**: Unique transaction hashes are counted and truncated to a daily grain based on UTC timestamps. This process ensures that complex transactions resulting in multiple receipts are only counted as a single protocol-level transaction. The counts are grouped by the Near Protocol product identifier and the specific chain ID.
- **Key fields**: `transaction_hash`, `block_timestamp`

### Component C: Data finalization and validation

- **Purpose**: Ensure schema consistency and data continuity for the final metric.
- **Logic**: The daily aggregates are cast to standardized data types and validated against supported chain and product identifiers. A zero-filling strategy is applied to the time series to ensure that any days without recorded transaction activity are explicitly represented with a value of zero, maintaining a continuous historical record.
- **Key fields**: `transaction_count`, `timestamp`

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

Confirmed transactions added to the blockchain.

NEAR ProtocolNEAR

Transaction count

Transaction count

Competitive landscape