website

github

Blockchains (L2)

Settlus

# Settlus Transaction count Methodology

## 1. Overview

The Settlus transaction count metric measures the daily number of unique transactions occurring on the Settlus blockchain. This metric answers the business question of transaction activity levels and user engagement on the Settlus network by counting distinct transactions grouped by recipient address on a daily basis. The calculation aggregates raw blockchain transaction data and applies standardized formatting and gap-filling logic to ensure consistent time series data.

## 2. Data sources

The metric uses the following raw data sources:
- **Blockchain transaction records**: Raw transaction data from the Settlus blockchain network containing transaction hashes, block timestamps, and participant addresses
- **Transaction metadata**: Block-level information including precise timestamps for temporal aggregation

## 3. Step-by-step calculation

### Component A: Transaction data standardization
- **Purpose**: Extracts and standardizes raw transaction data from the Settlus blockchain
- **Logic**: The system retrieves transaction records from Settlus blockchain data, casting key fields to appropriate data types for consistency. Each transaction record includes the `block_timestamp` for temporal analysis, `transaction_hash` for unique identification, `from_address` and `to_address` for participant tracking, and adds a chain identifier field set to 'settlus' for multi-chain compatibility
- **Key fields**: `block_timestamp` (transaction timing), `transaction_hash` (unique transaction identifier), `from_address` (sender), `to_address` (recipient), `chain` (blockchain identifier)

### Component B: Daily transaction aggregation
- **Purpose**: Counts unique transactions per day grouped by recipient address and metadata dimensions
- **Logic**: The system truncates transaction timestamps to daily boundaries to create consistent time periods. It then groups transactions by the truncated timestamp, recipient address (`to_address`), and various metadata dimensions. For each group, it counts the number of distinct transaction hashes to determine unique transaction volume. The grouping includes chain identification ('settlus'), market sector classification ('blockchains_l2'), business segment ('blockchain'), with product and contract fields set to null as they are not applicable for this blockchain-level metric
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct transaction hash count), `to_address` (recipient address), classification fields for reporting dimensions

### Final aggregation
- **Combining components**: The standardized transaction data flows directly into the daily aggregation component, with no complex joining required since both operate on the same transaction dataset
- **Currency conversion**: Not applicable for transaction count metrics as this measures transaction volume rather than monetary value
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day granularity, ensuring consistent 24-hour periods regardless of specific transaction timing within each day
- **Final calculation**: The final metric value represents the count of distinct transaction hashes for each combination of day, recipient address, and metadata dimensions, with automatic gap-filling to ensure zero values for days with no transactions and schema validation to maintain data quality standards

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

Confirmed transactions added to the blockchain.

Settlus

Transaction count

Transaction count

Competitive landscape