Social

Story Protocol

# Story Protocol Transaction count Methodology

## 1. Overview

The Story transaction count metric measures the daily number of unique transactions on the Story blockchain. This metric provides insights into network activity and user engagement by counting distinct transactions that occur each day. The calculation aggregates raw Story blockchain transaction data on a daily basis, counting unique transaction hashes while grouping by recipient addresses to provide granular transaction volume analysis.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Story blockchain transactions**: Raw transaction records from the Story blockchain network containing transaction hashes, sender and recipient addresses, and block timestamps
- **Story block data**: Block timestamp information used for daily aggregation and time-based filtering

## 3. Step-by-step calculation

### Component A: Transaction facts preparation
- **Purpose**: Prepares raw Story transaction data for aggregation by standardizing data types and adding chain identification
- **Logic**: Raw Story blockchain transaction data is accessed and key fields are cast to appropriate data types. Each transaction record includes the `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, and a chain identifier set to 'story'. This component serves as a clean, typed interface to the raw blockchain transaction 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)

### Component B: Daily transaction aggregation
- **Purpose**: Aggregates transaction data on a daily basis and adds categorical metadata for reporting
- **Logic**: Transaction timestamps are truncated to day boundaries using timestamp truncation. For each day and `to_address` combination, the system counts distinct `transaction_hash` values to avoid double-counting. The aggregation includes metadata fields that classify the data: chain identifier as 'story', market sector as 'blockchains_l2' (indicating Layer 2 blockchain category), and business segment as 'blockchain'. Product and contract name fields are set to null as they are not applicable for this blockchain-level metric.
- **Key fields**: `timestamp` (daily boundary), `transaction_count` (distinct count of transaction hashes), `to_address` (recipient address for granular analysis)

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that validates the data schema, ensures consistent field types, and fills any missing days with zero values to maintain complete time series
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated to daily boundaries using day-level timestamp truncation, with incremental processing including a configurable lookback period to ensure data completeness
- **Final calculation**: The final metric represents the count of distinct transaction hashes per day per recipient address on the Story blockchain, with chain availability filtering applied to ensure data quality and completeness

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

Confirmed transactions added to the blockchain.

Story ProtocolIP

Transaction count

Transaction count

Competitive landscape