website

github

twitter

Blockchains (L1)

XDC Network

# XDC Network Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the XDC blockchain network per second on a daily basis. This metric provides insight into the network's throughput and activity levels by calculating the daily transaction volume divided by the number of seconds in a day (86,400). The calculation uses distinct transaction counts to avoid double-counting and provides a standardized measure of blockchain network performance.

## 2. Data sources

- **XDC blockchain transaction records**: Raw transaction data from the XDC network containing all executed transactions with timestamps, transaction hashes, sender/receiver addresses, and gas usage information
- **XDC token metadata**: Hardcoded native token information including the XDC token contract address and symbol for standardization

## 3. Step-by-step calculation

### Component A: XDC transaction fact layer
- **Purpose**: Standardizes raw XDC transaction data into a consistent format for metric calculations
- **Logic**: Raw transaction records from the XDC blockchain are processed and standardized. Each transaction record includes the block timestamp when the transaction was executed, unique transaction hash identifier, sender and receiver addresses, gas usage, and gas price. The native XDC token metadata is added with the hardcoded contract address `0x951857744785e80e2de051c32ee7b25f9c458c42` and symbol `XDC`. The chain identifier is set to `xdc` for all records.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction participants, `gas_used` and `gas_price` for execution costs, `token_address` and `token_symbol` for native token identification

### Component B: Daily transaction count aggregation
- **Purpose**: Calculates the total number of distinct transactions processed each day on the XDC network
- **Logic**: Transaction records are grouped by day using timestamp truncation to daily granularity. For each day, the calculation counts distinct transaction hashes to avoid any potential double-counting. The aggregation also groups by destination address (`to_address`) to maintain granular transaction tracking while summing to daily totals. Metadata fields are added including chain identifier (`xdc`), market sector (`blockchains_l1`), business segment (`blockchain`), and product identifier (`xdc`). The finalize macro ensures proper schema validation and fills any missing days with zero transaction counts.
- **Key fields**: `timestamp` truncated to day level, `transaction_count` as distinct count of `transaction_hash`, chain and product identifiers for categorization

### Final aggregation
- **Combining components**: The daily transaction counts serve as the base for the TPS calculation without additional component joining
- **TPS calculation**: Each day's total transaction count is divided by the number of seconds in a day (86,400) using safe division to handle any potential edge cases where daily counts might be zero or null
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation, with each day representing a 24-hour period from midnight to midnight
- **Final calculation**: The transactions per second value is computed as the total daily distinct transaction count divided by 86,400 seconds, providing the average TPS for that day. The finalize macro applies final schema validation and ensures any missing days are filled with zero values to maintain complete time series data.

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

Average confirmed user transactions added per second.

XDC NetworkXDC

Transactions per second

Transactions per second

Competitive landscape