Autonomous agents transact on Kite Chain with owner-set budgets, permissions and scope, settling payments in native stablecoins; gas is paid in whitelisted stablecoins while KITE is used for staking and coordination.

Kite is an EVM-compatible Proof-of-Stake Avalanche L1 (chain ID 2366) built as a settlement and coordination layer for autonomous AI agents. Agents get verifiable identities through Kite Passport and pay for services with sub-second deterministic finality, with dedicated agent pay lanes and native cross-chain messaging.

Kite is developed by the Kite AI team behind gokite.ai; KITE is the network's native utility token used for staking and coordination.

website

twitter

discord

Blockchains (L1)

Kite

# Transaction count Methodology

## Overview

Transaction count measures the number of confirmed transactions added to the blockchain. It reflects how actively users engage with the network.

## Data sources

- Raw blockchain transaction records and unique transaction hashes
- Block metadata and ledger headers
- Network performance APIs and daily monitoring statistics

## Common calculation approaches

### Transaction hash aggregation
Unique transaction hashes are aggregated daily from raw blockchain records to quantify network activity. For blockchains such as BNB Chain and Base, distinct hashes are counted from both Layer 1 and Layer 2 environments to provide a comprehensive view of transaction activity across the ecosystem.

### Block metadata extraction
Transaction totals are retrieved directly from block headers or ledger metadata. For example, on Solana, the `total_transaction_count` is extracted from block-level data to include all confirmed interactions, including asset transfers and program instructions. Similarly, transaction counts are derived from ledger records on the Stellar network.

### Statistical performance conversion
Daily totals are derived from high-frequency network performance metrics when direct hash counts are not the primary data source. On the Internet Computer, daily transaction counts are calculated by converting average transactions per second (TPS) statistics into 24-hour totals.

**Note:** The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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

Confirmed transactions added to the blockchain.

KiteKITE

Transaction count

Transaction count

Competitive landscape

Chain breakdown