website

twitter

discord

Blockchains (L2)

Shape

# Shape Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the Shape blockchain network per second on a daily basis. This metric provides insight into network activity and throughput capacity by calculating the daily transaction volume divided by the number of seconds in a day (86,400). The metric helps assess network utilization and compare activity levels across different time periods.

## 2. Data sources

- **Shape blockchain transactions**: Raw transaction records from the Shape network containing transaction hashes, block timestamps, sender and receiver addresses, and other transaction metadata
- **Chain availability data**: Configuration data that defines periods when Shape network data is available and reliable for analysis

## 3. Step-by-step calculation

### Component A: Raw transaction processing
- **Purpose**: Extract and standardize Shape blockchain transaction data for analysis
- **Logic**: Raw transaction records from the Shape network are processed to extract key transaction attributes. Block timestamps are cast to timestamp format, transaction hashes and addresses are cast to string format. Each record includes the `block_timestamp`, `transaction_hash`, `from_address`, and `to_address` fields. The chain identifier is set to 'shape' for all records to maintain consistency across the data pipeline.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `transaction_hash` (unique identifier for each transaction), `from_address` and `to_address` (sender and receiver addresses), and `chain` (set to 'shape')

### Component B: Daily transaction aggregation
- **Purpose**: Count the total number of unique transactions per day on the Shape network
- **Logic**: Transaction data is aggregated by truncating block timestamps to daily boundaries using day-level timestamp truncation. Transactions are grouped by the truncated timestamp, chain identifier, market sector, and business segment. The system counts distinct transaction hashes to ensure each unique transaction is counted only once, avoiding potential duplicates. Additional metadata fields are populated including timestamp grain set to 'day', chain identifier set to 'shape', market sector set to 'blockchains_l2', business segment set to 'blockchain', with product and contract name fields set to null.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (set to 'day'), `chain_id` (shape), `transaction_count` (distinct count of transaction hashes), `market_sector_id` and `business_segment_id` for categorization

### Component C: Transaction count finalization
- **Purpose**: Apply data quality controls and fill gaps in the transaction count data
- **Logic**: The finalized transaction count data undergoes schema validation to ensure consistency with the standard transaction count metric format. Missing days are identified and filled with zero values using a fill zeros strategy, ensuring continuous daily coverage without gaps. Data quality checks validate that all required fields are present and properly formatted.
- **Key fields**: All fields from the daily aggregation with validated schema and gap-filled data

### Final aggregation
- **Combining components**: The finalized daily transaction counts serve as the foundation for the TPS calculation
- **Per-second conversion**: Daily transaction counts are divided by the number of seconds in a day (86,400) using a safe division function to calculate the average transactions per second for each day
- **Time aggregation**: Data maintains daily grain boundaries, with each day's TPS representing the average rate for that 24-hour period
- **Final calculation**: The transactions per second value equals the daily transaction count divided by 86,400 seconds, providing the average TPS for each day. Chain availability filters are applied to exclude periods when Shape network data is unavailable or unreliable, ensuring only valid time periods are included in the final metric.

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

Average confirmed user transactions added per second.

ShapeSHAPE

Transactions per second

Transactions per second

Competitive landscape