Ajuna is a gaming blockchain built on Polkadot, focused on enabling performance and scalability, for web3 gaming supporting the Unity and Unreal Engine game engines.

website

twitter

github

discord

Blockchains (L2)

Ajuna Network

# Ajuna Network Transaction count Methodology

## 1. Overview

This metric measures the daily transaction count for the Ajuna blockchain ecosystem. It counts the number of unique transactions (called "extrinsics" in Substrate-based chains like Ajuna) that occur each day on the Ajuna network. The calculation uses an approximate distinct count methodology to efficiently process large volumes of transaction data while maintaining accuracy for daily aggregations.

## 2. Data sources

The calculation relies on the following raw data sources:
- **Ajuna blockchain extrinsic records**: Individual transaction records from the Ajuna blockchain containing timestamps, unique extrinsic identifiers, and transaction details
- **Chain availability configuration**: Metadata defining the operational periods and availability windows for the Ajuna chain to ensure accurate time-series reporting

## 3. Step-by-step calculation

### Component A: Transaction data extraction and preparation
- **Purpose**: Extracts and standardizes raw transaction data from the Ajuna blockchain
- **Logic**: The system retrieves individual extrinsic records from Ajuna blockchain data, casting the `block_timestamp` field to timestamp format and the `extrinsic_id` to string format for consistent processing. Each record is tagged with a standardized `chain_id` of 'ajuna' to identify the source blockchain network.
- **Key fields**: `block_timestamp` (when the transaction was included in a block), `extrinsic_id` (unique identifier for each transaction), `chain_id` (blockchain network identifier)

### Component B: Daily transaction aggregation  
- **Purpose**: Groups transactions by day and counts unique transactions per day
- **Logic**: Transaction timestamps are truncated to day-level granularity using timestamp truncation to create daily boundaries. The data is grouped by the truncated timestamp, timestamp grain ('day'), chain ID, and product ID. For each day, the system counts approximately distinct extrinsic IDs to determine the number of unique transactions. The product is hardcoded as 'Ajuna Substrate' to identify the specific blockchain ecosystem.
- **Key fields**: `timestamp` (truncated to daily boundaries), `timestamp_grain` (set to 'day'), `product_id` (set to 'Ajuna Substrate'), `transaction_count` (approximate count of distinct extrinsics)

### Final aggregation
- **Combining components**: The daily aggregated data flows through a finalization macro that standardizes the schema, validates data integrity, and ensures no gaps exist in the time series by filling missing days with zero transaction counts
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation, with incremental processing including a configurable lookback period to handle late-arriving data
- **Final calculation**: The final metric represents the approximate count of distinct extrinsic IDs (transactions) per day, filtered by chain availability periods to exclude data from times when the chain was not operational or data collection was unreliable

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

Confirmed transactions added to the blockchain.

Ajuna NetworkAJUN

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown