Collators aggregate parachain transactions block candidates and producing state transition proofs for validators based on those blocks.

Kilt is digital identity solution powered by Polkadot Relay chain.

KILT holders own and govern the protocol.

website

twitter

github

etherscan

Blockchains (L2)

Kilt

# Kilt Transaction count Methodology

## 1. Overview

Transaction count measures the total number of unique transactions (extrinsics) processed daily on the Kilt blockchain. This metric answers the fundamental question of blockchain activity and adoption by counting all distinct transaction executions per day. Kilt uses the term "extrinsics" for what are commonly called transactions on other blockchains, representing any external data or function call submitted to the Kilt network.

## 2. Data sources

The calculation relies on these underlying raw data sources:
- **Kilt blockchain extrinsics**: Raw transaction records from the Kilt blockchain containing all submitted extrinsics with their execution timestamps and unique identifiers
- **Chain availability configuration**: Data quality rules and coverage requirements to ensure reliable metric calculation

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Standardize and prepare raw Kilt extrinsics data for aggregation
- **Logic**: Raw Kilt blockchain extrinsics are processed to extract essential transaction information. Each extrinsic record is identified with a unique `extrinsic_id` and timestamped with its `block_timestamp` indicating when it was included in a block. The data is enriched with chain identification metadata, specifically marking transactions as originating from the 'kilt' blockchain
- **Key fields**: The `block_timestamp` field captures when transactions were processed, `extrinsic_id` provides unique transaction identification, and `chain_id` identifies the blockchain as 'kilt'

### Component B: Daily transaction aggregation
- **Purpose**: Count unique transactions on a daily basis with proper categorization
- **Logic**: Transaction timestamps are truncated to daily boundaries to group all transactions occurring within the same calendar day. The system counts distinct extrinsic identifiers to ensure no double-counting of transactions. Each daily aggregate is tagged with standard Token Terminal taxonomy including market sector identification as 'blockchains_l2' and business segment as 'blockchain'. Product identification is set to null as this metric applies to the entire Kilt protocol rather than specific products
- **Key fields**: The `timestamp` represents daily boundaries, `transaction_count` contains the distinct count of transactions, and taxonomy fields provide proper categorization for reporting

### Final aggregation
- **Combining components**: The prepared transaction data flows directly into the daily aggregation component where unique transaction counting occurs
- **Currency conversion**: Not applicable as transaction count is a volume metric rather than a financial metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation, with incremental processing including a lookback window to ensure data completeness for recent periods
- **Final calculation**: The final metric value equals the count of distinct `extrinsic_id` values grouped by daily timestamp boundaries, with standardization applied through the finalize macro to ensure schema compliance and gap filling with zeros where no transactions occurred

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

Confirmed transactions added to the blockchain.

KiltKILT

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown