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

Hedera is a decentralized enterprise-grade public network that uses proof-of-stake hashgraph consensus to offer low & fixed fees, 10k TPS, and instant transaction finality. Hedera was founded by Leemon Baird, Mance Harmon, etc. and launched in 2019.

HBAR holders own and govern the protocol. They currently take a cut of the total transaction and query fees paid by users (revenue). Hedera’s investors include BlockTower Capital, Continue Capital, Unanimous Capital, etc.

github

twitter

discord

website

Blockchains (L1)

Hedera

# Hedera Transaction count Methodology

## 1. Overview

The Hedera transaction count metric measures the total number of unique transactions processed on the Hedera network on a daily basis. This metric provides insight into the network activity and usage patterns by counting distinct transaction occurrences. The calculation follows Token Terminal's standardized methodology for blockchain transaction metrics, ensuring consistent measurement across different networks.

## 2. Data sources

- **Hedera blockchain transactions**: Complete transaction records from the Hedera network including transaction identifiers, timestamps, block information, fees, and transaction types
- **Token Terminal configuration**: Chain availability filters and data quality standards to ensure reliable metric calculation

## 3. Step-by-step calculation

### Component A: Raw transaction extraction
- **Purpose**: Collect comprehensive transaction data from the Hedera blockchain
- **Logic**: Extract all transaction records from Hedera blockchain data including key identifiers like `transaction_hash`, `transaction_id`, block information (`block_number`, `block_timestamp`), network details (`node`, `entity_id`), financial data (`fee_charged`), and transaction classification (`name` as transaction type). The data is filtered incrementally to process only recent transactions efficiently while maintaining historical completeness.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `transaction_id` for internal reference, `block_number` for blockchain position, `node` and `entity_id` for network routing, `fee_charged` for transaction costs, and transaction type classification

### Component B: Daily aggregation and standardization
- **Purpose**: Aggregate transaction counts to daily granularity and apply Token Terminal's standardized metric schema
- **Logic**: Truncate transaction timestamps to daily boundaries using day-level timestamp truncation. Count distinct transaction hashes within each day to ensure no double-counting of transactions. Apply Token Terminal's standard classification scheme labeling Hedera as chain identifier 'hedera', market sector 'blockchains_l1', and business segment 'blockchain'. Set timestamp grain to 'day' and product identifier to null since this is a network-level metric rather than product-specific.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (set to 'day'), `chain_id` (set to 'hedera'), `market_sector_id` (set to 'blockchains_l1'), `business_segment_id` (set to 'blockchain'), `product_id` (null for network-level metrics), `transaction_count` (distinct count of transaction hashes)

### Final aggregation
- **Combining components**: The raw transaction data flows directly into the daily aggregation component where transactions are grouped by daily timestamp boundaries
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent 24-hour periods regardless of block timing variations
- **Schema validation and gap filling**: Apply Token Terminal's finalization macro to validate the metric schema, ensure required fields are present, and fill any missing days with zero transaction counts using the 'fill_zeros' strategy
- **Data quality filtering**: Apply chain availability filters to exclude periods where Hedera data may be incomplete or unreliable, ensuring metric accuracy and consistency
- **Final calculation**: The result is a daily time series showing the count of distinct transactions processed on the Hedera network each day, formatted according to Token Terminal's standardized metric schema

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

Confirmed transactions added to the blockchain.

HederaHBAR

Transaction count

Transaction count

Competitive landscape