Social

Story Protocol

# Story Protocol Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Story Protocol blockchain over a given day. This metric provides insight into the network's transaction processing capacity and usage patterns. The calculation takes the total number of unique transactions in a day and divides by the number of seconds in that day (86,400) to produce an average throughput rate.

## 2. Data sources

- **Story Protocol blockchain transactions**: Raw transaction records from the Story Protocol blockchain including transaction metadata, timestamps, and participant addresses
- **Block timestamps**: Precise timing data for when each transaction was included in a block on the Story Protocol network
- **Transaction identifiers**: Unique transaction hashes used to ensure accurate counting without duplicates
- **Address data**: Sender and receiver wallet addresses for each transaction on the Story Protocol network

## 3. Step-by-step calculation

### Component A: Raw transaction data extraction
- **Purpose**: Extract and standardize core transaction data from the Story Protocol blockchain
- **Logic**: Raw Story Protocol blockchain transaction records are accessed and key fields are extracted including block timestamps, transaction hashes, sender addresses (`from_address`), and receiver addresses (`to_address`). All fields are cast to appropriate data types for consistency and a chain identifier of 'story' is added to distinguish this blockchain's data
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction participants

### Component B: Daily transaction count aggregation  
- **Purpose**: Count unique transactions per day while maintaining address-level granularity
- **Logic**: Transaction data is grouped by calendar day using timestamp truncation to day-level granularity. For each day and destination address combination, distinct transaction hashes are counted to avoid double-counting. Additional metadata is assigned including chain identifier ('story'), market sector ('blockchains_l2'), and business segment ('blockchain'). Any missing days in the data are filled with zero transaction counts to ensure complete time series
- **Key fields**: `timestamp` truncated to day level, `transaction_count` as distinct hash count, `to_address` for granular tracking, chain and sector classification fields

### Final aggregation
- **Combining components**: Daily transaction counts are summed across all addresses for each day to get total daily transaction volume for the Story Protocol network
- **Currency conversion**: Not applicable - this metric measures transaction volume, not monetary value
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with each day representing a complete 24-hour period
- **Final calculation**: Transactions per second is calculated by dividing the total number of unique transactions in each day by 86,400 (the number of seconds in a day). The formula is: TPS = daily_transaction_count ÷ 86,400. Chain availability filtering is applied to ensure data quality and completeness

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

Average confirmed user transactions added per second.

Story ProtocolIP

Transactions per second

Transactions per second

Competitive landscape