Validators process transactions and receive fees from users (supply-side fees).

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Transaction count Methodology

## 1. Overview

Transaction count measures the total number of unique transactions executed on the Astar network per day. This metric captures transaction activity across both the native Substrate layer and the Ethereum Virtual Machine (EVM) execution layer of Astar, providing a comprehensive view of network usage. The calculation counts distinct transactions daily and ensures data continuity through gap-filling strategies.

## 2. Data sources

The calculation relies on the following raw blockchain data sources:

- **Astar native extrinsics**: Native Substrate-based transaction records from the Astar parachain, containing block timestamps and unique extrinsic identifiers
- **Astar EVM execution events**: Ethereum Virtual Machine transaction execution events from the 'ethereum' pallet, specifically `Executed` method events that represent completed EVM transactions on Astar
- **Chain availability configuration**: Internal configuration data that defines which chains and time periods have reliable data coverage

## 3. Step-by-step calculation

### Component A: Native astar transactions
- **Purpose**: Captures all native Substrate-based transactions on the Astar parachain
- **Logic**: Extracts transaction records from Astar extrinsics data, applying safe casting to ensure data type consistency for `block_timestamp` and `extrinsic_id` fields. Each record is labeled with chain identifier 'astar' to distinguish it from EVM transactions
- **Key fields**: `block_timestamp` for timing, `extrinsic_id` as the unique transaction identifier, and `chain_id` set to 'astar'

### Component B: Astar EVM transactions  
- **Purpose**: Captures all Ethereum Virtual Machine transactions executed on Astar's EVM layer
- **Logic**: Filters events data to include only records where `event_pallet` equals 'ethereum' and `event_method` equals 'Executed', indicating successful EVM transaction execution. Creates composite unique identifiers by concatenating `extrinsic_id` with `event_index` to ensure uniqueness across multiple EVM events within the same extrinsic
- **Key fields**: `block_timestamp` for timing, composite `extrinsic_id` combining original extrinsic ID with event index, and `chain_id` set to 'astarevm'

### Final aggregation
- **Combining components**: Both native Astar and EVM transaction datasets are combined using a union operation to create a comprehensive transaction dataset covering all transaction types on the network
- **Time aggregation**: Block timestamps are truncated to daily boundaries using day-level granularity, with transactions grouped by date, chain identifier, and product identifier ('Astar Substrate')
- **Transaction counting**: Uses approximate count distinct function on `extrinsic_id` to count unique transactions per day, optimizing performance for large datasets while maintaining accuracy
- **Gap filling**: Applies standardization macro with 'fill_zeros' strategy to ensure continuous daily time series, filling missing days with zero transaction counts
- **Final calculation**: The result is daily transaction counts by chain type (native vs EVM), filtered through chain availability rules to ensure data quality and exclude periods with incomplete or unreliable data coverage

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

Confirmed transactions added to the blockchain.

AstarASTR

Transaction count

Transaction count

Competitive landscape

Chain breakdown