website

github

twitter

Blockchains (L1)

XDC Network

# XDC Network Transaction count Methodology

## 1. Overview

The XDC transaction count metric measures the total number of unique transactions processed on the XDC Network on a daily basis. This metric provides insight into network activity and adoption by counting all distinct transaction hashes that occur each day. The calculation aggregates raw blockchain transaction data into daily totals while ensuring data completeness through gap-filling logic that assigns zero values to days with no transaction activity.

## 2. Data sources

The calculation relies on the following raw data sources:

- **XDC blockchain transaction records**: Complete transaction data from XDC Network nodes including transaction identifiers, participant addresses, and execution details
- **XDC network timestamps**: Block-level timestamps from the XDC blockchain indicating when transactions were processed and included in blocks
- **Transaction metadata**: Gas consumption metrics and pricing data for each transaction on the XDC network
- **Network address data**: Sender (`from_address`) and recipient (`to_address`) information for each transaction

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Standardize and clean raw XDC transaction data for aggregation
- **Logic**: Raw XDC blockchain transaction records are processed to ensure consistent data types and formats. The system applies safe casting operations to convert `block_timestamp` to timestamp format, `transaction_hash` to string format, and address fields (`from_address`, `to_address`) to standardized string formats. Gas-related fields (`gas_used`, `gas_price`) are converted to big numeric format for precise calculations. Additional metadata is added including a hardcoded `token_address` value and `token_symbol` set to 'XDC' to maintain consistency with other blockchain metrics.
- **Key fields**: `block_timestamp` for temporal aggregation, `transaction_hash` for unique transaction identification, `from_address` and `to_address` for transaction routing, `gas_used` and `gas_price` for network utilization metrics

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions per day while maintaining dimensional breakdown by recipient address
- **Logic**: Transactions are grouped by daily time boundaries using timestamp truncation to day-level granularity. The system counts distinct `transaction_hash` values for each combination of day and `to_address` to ensure no transaction is double-counted. Additional metadata dimensions are added including `chain_id` set to 'xdc', `market_sector_id` set to 'blockchains_l1', `business_segment_id` set to 'blockchain', and `product_id` set to 'xdc' for categorization purposes. The `contract_name` field is set to null as this metric tracks network-level activity rather than specific smart contract usage.
- **Key fields**: `timestamp` truncated to daily boundaries, `transaction_count` as the distinct count of transaction hashes, `to_address` for recipient-level breakdown

### Final aggregation
- **Combining components**: The daily transaction aggregations are processed through a finalization macro that validates the data schema, ensures temporal continuity, and applies gap-filling logic
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with incremental processing that looks back one day plus a configurable lookback period to handle late-arriving data
- **Gap filling**: The finalization process implements a 'fill_zeros' strategy that identifies missing dates in the time series and creates records with zero transaction counts to maintain data completeness
- **Final calculation**: The metric represents the count of distinct transaction hashes per day, filtered by chain availability settings to ensure only active network periods are included in the final results

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

Confirmed transactions added to the blockchain.

XDC NetworkXDC

Transaction count

Transaction count

Competitive landscape