twitter

website

github

Blockchains (L2)

Nodle

# Nodle Transaction count Methodology

## 1. Overview

The Nodle transaction count metric measures the daily number of unique transactions processed on the Nodle blockchain. This metric provides insight into network activity and adoption by counting distinct extrinsic (transaction) identifiers submitted to the Nodle network each day. The calculation aggregates raw blockchain transaction data into daily totals, ensuring complete time series data with proper handling of missing periods.

## 2. Data sources

The metric relies on the following data sources:
- **Nodle blockchain extrinsics**: Raw transaction records from the Nodle blockchain containing extrinsic identifiers, block timestamps, and transaction metadata
- **Chain availability data**: Configuration data that defines periods when Nodle chain data is considered reliable and available for metric calculation

## 3. Step-by-step calculation

### Component A: Transaction fact preparation
- **Purpose**: Standardizes raw Nodle blockchain transaction data into a consistent format for downstream processing
- **Logic**: Raw extrinsic records from the Nodle blockchain are selected and type-cast to ensure data quality. Each record represents a unique transaction (extrinsic) with its associated block timestamp and chain identifier
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `extrinsic_id` (unique transaction identifier), `chain_id` (set to 'nodle')

### Component B: Daily transaction aggregation  
- **Purpose**: Aggregates individual transactions into daily counts while adding required metadata for the metrics framework
- **Logic**: Transactions are grouped by day using timestamp truncation to day granularity. The calculation counts distinct `extrinsic_id` values to ensure each unique transaction is counted exactly once, even if there are duplicate records. Additional metadata fields are added including market sector classification ('blockchains_l2'), business segment ('blockchain'), and chain identification ('nodle')
- **Key fields**: `timestamp` (truncated to day), `transaction_count` (distinct count of extrinsic IDs), classification metadata fields

### Final aggregation
- **Combining components**: The daily aggregation serves as the primary data source, with the finalization macro applying additional processing
- **Currency conversion**: Not applicable for transaction count metrics
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, ensuring consistent 24-hour periods
- **Final calculation**: The finalize_metric_transaction_count macro validates the schema, ensures proper ID formatting, and fills any gaps in the time series with zero values for days with no transactions. A chain availability filter excludes data from periods when the Nodle chain was not reliably operational. The result is a complete daily time series showing the count of unique transactions processed by the Nodle blockchain each day.

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

Confirmed transactions added to the blockchain.

NodleNODL

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown