website

Blockchains (L2)

Superseed

# Superseed Transaction count Methodology

## 1. Overview

The SuperSeed transaction count metric measures the daily number of unique transactions on the SuperSeed Layer 2 blockchain, segmented by recipient address. This metric provides insight into network activity and usage patterns by tracking the volume of distinct transactions occurring each day. The calculation aggregates raw blockchain transaction data into daily counts, ensuring no duplicate transactions are included and providing complete time series data with zero-filled gaps.

## 2. Data sources

The metric relies on the following raw data sources:
- **SuperSeed blockchain transactions**: Complete transaction records from the SuperSeed L2 blockchain including transaction hashes, sender addresses, recipient addresses, and block timestamps
- **SuperSeed block data**: Block timestamp information used to determine when transactions occurred

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extracts and standardizes raw SuperSeed transaction data
- **Logic**: Retrieves all transaction records from SuperSeed blockchain data, casting core fields to appropriate data types. Each record includes the unique `transaction_hash`, `from_address` (sender), `to_address` (recipient), and `block_timestamp` indicating when the transaction was included in a block. The chain identifier is set to 'superseed' for all records.
- **Key fields**: `transaction_hash` for uniqueness, `from_address` and `to_address` for transaction parties, `block_timestamp` for temporal grouping

### Component B: Daily aggregation
- **Purpose**: Groups transactions into daily buckets and counts unique transactions per recipient
- **Logic**: Block timestamps are truncated to daily boundaries using day-level granularity, creating uniform daily time periods. Transactions are grouped by the truncated timestamp and `to_address` (recipient address). Within each group, distinct transaction hashes are counted to ensure no duplicates are included in the final count. Standard metadata fields are added including 'superseed' as `chain_id`, 'blockchains_l2' as `market_sector_id`, and 'blockchain' as `business_segment_id`.
- **Key fields**: `timestamp` (daily boundary), `to_address` (transaction recipient), `transaction_count` (distinct hash count)

### Final aggregation
- **Combining components**: The daily aggregated data is processed through a finalization macro that validates the data schema, ensures proper field formatting, and fills any gaps in the time series with zero values where no transactions occurred
- **Currency conversion**: Not applicable - this is a count metric without monetary values
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, ensuring consistent 24-hour periods aligned with UTC dates
- **Final calculation**: The final metric value represents the count of distinct transaction hashes that occurred on each day for each recipient address on the SuperSeed blockchain, with zero values filled for days with no activity and chain availability filters applied based on configuration settings

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

Confirmed transactions added to the blockchain.

SuperseedSUPR

Archived

Transaction count

Transaction count

Competitive landscape