twitter

website

github

Blockchains (L2)

Nodle

# Nodle Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed per second on the Nodle blockchain over daily time periods. This metric provides insight into network activity and throughput capacity by taking the total daily transaction count and dividing it by the number of seconds in a day (86,400). The calculation uses distinct transaction identifiers to ensure accurate counting and applies gap-filling logic to maintain complete time series data.

## 2. Data sources

The calculation relies on the following data sources:
- **Nodle blockchain extrinsics**: Raw transaction records from the Nodle blockchain containing transaction identifiers and block timestamps
- **Chain availability configuration**: Metadata that defines data availability requirements and quality standards for the Nodle network

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and standardize transaction data from raw Nodle blockchain records
- **Logic**: Raw extrinsic records from the Nodle blockchain are processed to extract transaction identifiers and block timestamps. The `block_timestamp` field is cast to timestamp format, and the `extrinsic_id` field is cast to string format for consistency. Each record is labeled with 'nodle' as the `chain_id` to identify the source blockchain.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `extrinsic_id` (unique transaction identifier), `chain_id` (blockchain identifier set to 'nodle')

### Component B: Daily transaction count aggregation
- **Purpose**: Count unique transactions per day and assign metadata classifications
- **Logic**: Transaction data is aggregated to daily boundaries using timestamp truncation to the day level. Unique transactions are counted using the distinct `extrinsic_id` values within each day. Additional metadata is assigned including `market_sector_id` as 'blockchains_l2', `business_segment_id` as 'blockchain', and `product_id` as null. The aggregation groups by timestamp, timestamp grain, chain ID, and metadata fields.
- **Key fields**: `timestamp` (daily boundary), `timestamp_grain` (set to 'day'), `transaction_count` (count of distinct extrinsic IDs per day), metadata classification fields

### Final aggregation
- **Combining components**: The daily transaction counts are processed through the transactions per second calculation by dividing the `transaction_count` by the number of seconds in a day
- **Currency conversion**: Not applicable for this transaction volume metric
- **Time aggregation**: Daily boundaries are maintained, with each day representing a complete 24-hour period from midnight to midnight
- **Final calculation**: Transactions per second is calculated as the daily transaction count divided by 86,400 seconds using safe division to handle edge cases. The result represents the average transactions per second for each day. Gap-filling logic ensures complete time series by inserting zero values for any missing dates to maintain data continuity.

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

Average confirmed user transactions added per second.

NodleNODL

Archived

Transactions per second

Transactions per second

Competitive landscape

Chain breakdown