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

Ink is an Ethereum Layer 2 (L2) blockchain built on Optimism's Superchain, focused on providing a secure, scalable infrastructure for Web3 applications.

Kraken team owns and governs the protocol. Kraken's investors include RIT Capital Partners, Hummingbird Ventures, Money Partners Group, etc.

github

website

twitter

discord

Blockchains (L2)

# Ink Transaction count Methodology

## 1. Overview

Transaction count measures the total number of unique transactions executed on the INK blockchain per day. This metric tracks blockchain usage and activity levels by counting distinct transaction hashes, providing insight into network utilization and adoption trends. The calculation aggregates all transaction activity on a daily basis, ensuring each transaction is counted exactly once regardless of its complexity or gas usage.

## 2. Data sources

The metric uses the following raw data sources:
- **INK blockchain transaction data**: Raw transaction records from the INK blockchain including transaction identifiers, timestamps, sender and receiver addresses, and gas usage information
- **Chain availability configuration**: Metadata defining valid data coverage periods to ensure accurate reporting during network outages or data collection issues

## 3. Step-by-step calculation

### Component A: Transaction data preparation
- **Purpose**: Extract and standardize raw INK blockchain transaction data for analysis
- **Logic**: Raw INK blockchain transaction records are selected and cleaned. All relevant fields are cast to appropriate data types to handle potential data quality issues. The system adds metadata including the native token address (`0x4200000000000000000000000000000000000006`) and symbol (`ETH`) for INK transactions. Transaction timestamps, hashes, sender and receiver addresses, and gas usage metrics are preserved for downstream processing.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `from_address` and `to_address` for transaction parties, gas usage fields (`gas_used`, `l1_gas_used`, `l1_gas_price`, `l1_fee_scalar`, `gas_price`) for network cost tracking

### Component B: Daily transaction aggregation  
- **Purpose**: Count unique transactions per day to create the core transaction count metric
- **Logic**: Transaction data is grouped by day using timestamp truncation to day-level granularity. For each day, the system counts distinct transaction hashes to ensure each transaction is counted exactly once, avoiding double-counting scenarios. The aggregation includes metadata classification with chain identifier (`ink`), market sector (`blockchains_l2`), and business segment (`blockchain`). Transactions are grouped by recipient address (`to_address`) to enable granular analysis while maintaining daily totals.
- **Key fields**: `timestamp` truncated to day level, `transaction_count` as distinct count of `transaction_hash`, `to_address` for granular grouping

### Final aggregation
- **Combining components**: The daily transaction counts are processed through finalization logic that validates data quality and ensures consistent schema structure
- **Time aggregation**: Daily boundaries are applied using timestamp truncation, with incremental processing handling recent data updates efficiently through a configurable lookback window
- **Data validation**: Schema validation ensures all required fields are present and properly formatted, with ID validation confirming data integrity
- **Gap filling**: Days without any transactions are filled with zero values using the fill_zeros strategy to maintain complete time series data
- **Availability filtering**: Chain availability filters exclude time periods where data collection was incomplete or the network experienced outages, ensuring accurate reporting of actual network activity

## Final calculation

The final transaction count represents the total number of unique transactions executed on the INK blockchain per day. Each transaction hash is counted exactly once regardless of complexity, gas usage, or transaction value. The metric provides a pure measure of transaction volume and network activity, with gaps filled as zeros for days without activity and invalid periods excluded based on data availability rules.

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

Confirmed transactions added to the blockchain.

Ink

Transaction count

Transaction count

Competitive landscape

Chain breakdown