Kinto batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Kinto is an L2 smart contract platform for decentralized applications on Ethereum with enforced account abstraction and KYC'd users. Kinto was founded by Ramon Recuero, Víctor Sánchez, and Alan Keegan and launched in 2024.

Kinto team & investors own and govern the protocol. Kinto’s investors include ParaFi Capital, Kyber Capital, The Spartan Group, etc.

github

twitter

discord

website

Blockchains (L2)

Kinto

# Kinto Transaction count Methodology

## 1. Overview

The Kinto transaction count metric measures the daily volume of unique transactions processed on the Kinto L2 blockchain. This metric provides insight into network activity and adoption by counting distinct transactions sent to each recipient address on a daily basis. The calculation aggregates raw blockchain transaction data into daily summaries, ensuring data quality through standardized processing and gap-filling procedures.

## 2. Data sources

The calculation relies on these primary data sources:
- **Kinto blockchain transactions**: Complete transaction records from the Kinto L2 blockchain, including transaction hashes, sender and recipient addresses, and block timestamps
- **Chain availability data**: Configuration data that defines active operational periods for the Kinto blockchain to ensure metrics are only calculated during valid time ranges

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Clean and standardize raw Kinto transaction data for further processing
- **Logic**: Raw transaction records from the Kinto blockchain are processed to ensure data quality and consistency. All key fields including `block_timestamp`, `transaction_hash`, `from_address`, and `to_address` are cast to appropriate data types using safe casting to handle any malformed data. A chain identifier is added to mark all records as belonging to the Kinto network.
- **Key fields**: `block_timestamp` for temporal grouping, `transaction_hash` for unique transaction identification, `from_address` and `to_address` for transaction participants, and `chain` identifier set to "kinto"

### Component B: Daily transaction aggregation
- **Purpose**: Aggregate transaction data into daily counts grouped by recipient address
- **Logic**: The prepared transaction data is grouped by day using timestamp truncation to daily boundaries. For each day and recipient address combination, the system counts distinct transaction hashes to ensure accurate counting without duplicates. Additional metadata fields are added including timestamp grain set to "day", chain identifier as "kinto", market sector as "blockchains_l2", and business segment as "blockchain". Product and contract name fields are set to null as this metric tracks general network activity rather than specific applications.
- **Key fields**: `timestamp` truncated to day boundaries, `transaction_count` as the distinct count of `transaction_hash` values, `to_address` for grouping transactions by recipient, and various classification fields for data organization

### Final aggregation
- **Combining components**: The daily aggregated data is processed through a standardized finalization macro that validates the metric schema, ensures proper field types and naming conventions, and applies data quality checks
- **Currency conversion**: Not applicable for this transaction count metric
- **Time aggregation**: Data is aggregated to daily boundaries using timestamp truncation, with gaps filled using a "fill_zeros" strategy to ensure complete daily time series
- **Final calculation**: The final metric represents the count of distinct transactions sent to each recipient address on each day, filtered to exclude periods when the Kinto chain was not operationally available

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

Confirmed transactions added to the blockchain.

Kinto

Archived

Transaction count

Transaction count

Competitive landscape

Chain breakdown