website

twitter

discord

Blockchains (L2)

Shape

# Shape Transaction count Methodology

## 1. Overview

The Shape transaction count metric measures the daily number of unique transactions processed on the Shape blockchain. This metric captures on-chain activity by counting distinct transactions that occur each day, providing insight into network usage and adoption. The calculation aggregates raw blockchain transaction data by day and ensures data completeness through gap-filling and validation processes.

## 2. Data sources

- **Shape blockchain transaction records**: Raw transaction data from the Shape L2 blockchain containing transaction hashes, sender addresses, recipient addresses, and execution details
- **Shape blockchain block data**: Block-level data with timestamps that provide temporal context for when transactions were processed on-chain

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Standardize raw Shape blockchain transaction data for analysis
- **Logic**: Raw transaction records are extracted from Shape blockchain data and standardized. The process casts core fields including `block_timestamp`, `transaction_hash`, `from_address`, and `to_address` to ensure consistent data types. A chain identifier is added to mark all records as originating from Shape
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for uniqueness counting, `from_address` and `to_address` for transaction participants, and `chain` identifier set to 'shape'

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions by day with proper metadata classification
- **Logic**: Block timestamps are truncated to daily boundaries to group transactions by calendar day. Transactions are grouped by day, chain metadata fields, and recipient address. Within each group, distinct transaction hashes are counted to ensure each unique transaction is counted exactly once, even if it appears in multiple records. Metadata fields classify Shape as a Layer 2 blockchain in the blockchain business segment
- **Key fields**: `timestamp` truncated to day level, `transaction_count` as count of distinct `transaction_hash` values, `chain_id` set to 'shape', `market_sector_id` as 'blockchains_l2', and `business_segment_id` as 'blockchain'

### Final aggregation
- **Combining components**: The daily aggregated transaction counts are processed through a finalization macro that validates the output schema and ensures data completeness
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Daily boundaries are established by truncating block timestamps to day level, with each day representing a 24-hour period in the blockchain's timezone
- **Final calculation**: The metric represents the count of distinct transaction hashes that occurred on Shape blockchain each day, with any missing days filled with zero values to maintain a complete time series. Results are filtered based on chain availability configuration to ensure only valid time periods are included

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

Confirmed transactions added to the blockchain.

ShapeSHAPE

Transaction count

Transaction count

Competitive landscape