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 Average fees per user (AFPU) Methodology

## 1. Overview

Average Fees Per User (AFPU) measures the average daily fee revenue generated per active user on the Hedera network. This metric answers the business question: "How much fee revenue does each active user generate on average per day?" The calculation divides total daily fees (in USD) by the count of daily active users, where active users are defined as addresses that initiate outgoing HBAR transfers.

## 2. Data sources

The calculation relies on several core data sources from the Hedera blockchain:

- **Hedera transaction records**: Complete transaction data including the `fee_charged` field, which contains transaction fees in tinybars (HBAR's smallest unit with 8 decimal places)
- **Hedera HBAR transfer events**: Native token transfer records containing sender and recipient addresses, transfer amounts, and transaction metadata
- **End-of-day HBAR price feeds**: Daily closing prices used to convert native HBAR fees to USD values
- **Hedera blockchain metadata**: Block timestamps, transaction hashes, block numbers, and network identifiers for proper transaction tracking and time-based aggregation

## 3. Step-by-step calculation

### Component A: Daily fees calculation
- **Purpose**: Calculate total daily fee revenue in USD from all Hedera transactions
- **Logic**: Extract transaction fees from Hedera transaction records using the `fee_charged` field, which represents fees paid in tinybars. Convert these fees to standard HBAR units by dividing by 1e8 (since HBAR has 8 decimal places). Aggregate all fees by day using timestamp truncation to daily boundaries. Apply end-of-day HBAR price feeds to convert the native HBAR fee totals to USD values for standardized reporting
- **Key fields**: `fee_charged` (transaction fees in tinybars), `block_timestamp` (for daily aggregation), `total_fees` (aggregated native fees), `fees` (USD-converted fees)

### Component B: Daily active users calculation  
- **Purpose**: Count unique users who actively participated in the network each day
- **Logic**: Identify active users from Hedera HBAR transfer events by filtering for transfers where `transfer_amount` is negative, indicating outgoing transfers from sender addresses. This approach defines active users as those initiating transactions rather than passive recipients. Extract the `account_address` from these outgoing transfers and aggregate by day using timestamp truncation. Use HyperLogLog (HLL) data structures to efficiently count unique user addresses per day, enabling scalable distinct counting across large datasets. Data processing is optimized by splitting between historical records (pre-2025) and incremental recent data (2025+)
- **Key fields**: `account_address` (user addresses), `transfer_amount` (negative values indicate senders), `block_timestamp` (for daily aggregation), `user_dau` (unique daily active users)

### Final aggregation
- **Combining components**: The fees and user metrics are joined by date to create matched daily pairs of total fees and active user counts
- **Currency conversion**: All fees are converted to USD using end-of-day HBAR price feeds to ensure consistent currency reporting across time periods
- **Time aggregation**: Both fees and user counts use daily timestamp truncation to ensure matching time boundaries for the division calculation  
- **Final calculation**: AFPU is calculated by dividing the total daily fees (in USD) by the daily active user count for each day. The `calculate_arpu` macro performs this division, handling cases where user counts might be zero. The `finalize_metric_afpu` macro then applies the standard schema, validates data integrity, and fills any missing days with zero values to ensure complete time series coverage

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

HederaHBAR

Average fees per user (AFPU)

Average fees per user (AFPU)

Competitive landscape