website

twitter

discord

Blockchains (L2)

Soneium

# Soneium Transaction count Methodology

## 1. Overview

The Soneium transaction count metric measures daily transaction activity on the Soneium blockchain network. This metric counts the number of unique transactions per day, segmented by destination address (`to_address`). The calculation aggregates raw blockchain transaction data to daily granularity and provides a comprehensive view of network activity. This metric answers the business question: "How many unique transactions occurred on Soneium each day, and how are they distributed across different destination addresses?"

## 2. Data sources

The calculation uses the following underlying data sources:

- **Soneium blockchain transaction data**: Raw transaction records from the Soneium blockchain containing transaction hashes, timestamps, sender addresses, and recipient addresses
- **Chain availability configuration**: Metadata defining when Soneium blockchain data collection was active and reliable

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Standardizes raw Soneium transaction data and ensures consistent field types
- **Logic**: Raw Soneium blockchain transaction records are processed to cast all fields to appropriate data types. The `block_timestamp` field is converted to timestamp format, while `transaction_hash`, `from_address`, and `to_address` are standardized as string types. A chain identifier field is added with the value 'soneium' to distinguish this blockchain's data
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `transaction_hash` (unique transaction identifier), `from_address` (transaction sender), `to_address` (transaction recipient), and `chain` (blockchain identifier)

### Component B: Daily transaction aggregation
- **Purpose**: Groups transactions by day and destination address, counting unique transactions for each combination
- **Logic**: Transaction data is truncated to daily boundaries using the `block_timestamp` field. For each day and each unique `to_address`, the system counts distinct transaction hashes to avoid double-counting any transactions. Standard metadata fields are added including chain identifier ('soneium'), market sector ('blockchains_l2'), business segment ('blockchain'), with null values for product and contract identifiers since this is a chain-level metric
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` ('day'), `chain_id` ('soneium'), `to_address` (destination address), and `transaction_count` (count of distinct transaction hashes)

### Final aggregation
- **Combining components**: The daily aggregated data flows through the `finalize_metric_transaction_count` macro which applies standardized schema validation, ensures all required identifier fields are present, and implements a fill-zeros strategy for days with no transaction activity
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Transactions are aggregated using daily boundaries based on block timestamp truncation. The incremental processing includes a configurable lookback period to handle late-arriving or updated transaction data
- **Final calculation**: The final metric value represents the count of distinct transaction hashes per day per destination address on the Soneium blockchain. Chain availability filtering removes any data from periods when Soneium blockchain data collection was not operational, ensuring data quality and consistency in the final results

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

Confirmed transactions added to the blockchain.

Soneium

Transaction count

Transaction count

Competitive landscape

Chain breakdown