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

Stellar is a distributed ledger for transfer and store of value (a blockchain). Stellar was founded by Jed McCaleb launched in 2014.

XLM holders own and govern the protocol. They currently take all of the total transaction fees paid by users (revenue).

github

twitter

discord

etherscan

website

Blockchains (L1)

Stellar

# Stellar Transaction count Methodology

## 1. Overview

The Stellar transaction count metric measures the total number of unique transactions executed on the Stellar blockchain network on a daily basis. This metric provides insight into the overall activity and usage of the Stellar network by counting each distinct transaction that occurred within a 24-hour period. The calculation aggregates raw Stellar blockchain transaction data to produce daily transaction volume figures, which serve as a key indicator of network adoption and user activity.

## 2. Data sources

The calculation relies on the following data sources:
- **Stellar blockchain transaction records**: Complete transaction data from the Stellar network including transaction identifiers, execution timestamps, and transaction metadata
- **Stellar network ledger data**: Block-level timestamp information and transaction ordering data from the Stellar distributed ledger
- **Transaction execution data**: Information about transaction success status, fees charged, operation counts, and source account details from Stellar network validators

## 3. Step-by-step calculation

### Component A: Transaction fact table preparation
- **Purpose**: Standardizes raw Stellar transaction data into a consistent format for analysis
- **Logic**: Extracts transaction records from Stellar blockchain data, including `transaction_hash`, `block_timestamp`, `source_account`, `fee_charged`, `successful` status, and `operation_count`. The data is filtered to include only transactions within the specified time range for incremental processing. Each transaction record is standardized with consistent data types and chain metadata identifiers.
- **Key fields**: `transaction_hash` serves as the unique identifier for each transaction, `block_timestamp` provides the exact execution time, `source_account` identifies the transaction originator, and `successful` indicates whether the transaction was executed successfully

### Component B: Daily transaction aggregation  
- **Purpose**: Groups transaction data by day and counts distinct transactions
- **Logic**: Transaction timestamps are truncated to day-level granularity using daily time boundaries. For each day, the system counts distinct `transaction_hash` values to determine the total number of unique transactions. The aggregation includes metadata fields identifying the data as belonging to the Stellar chain within the layer-1 blockchain market sector.
- **Key fields**: `timestamp` represents the daily time boundary, `transaction_count` contains the count of distinct transactions for that day, and chain identification fields classify the data appropriately

### Final aggregation
- **Combining components**: The daily transaction counts are processed through a finalization macro that validates the data schema and ensures consistency
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated at daily boundaries, with each day representing a complete 24-hour period in UTC time
- **Final calculation**: The final metric represents the count of distinct transaction hashes that occurred within each daily time period, with gaps in the time series filled with zero values to maintain data completeness. Chain availability filters ensure data quality standards are met before final output.

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

Confirmed transactions added to the blockchain.

StellarXLM

Transaction count

Transaction count

Competitive landscape