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

Polygon is a smart contract platform for decentralized applications & interoperability platform for blockchains. Polygon was founded by Jaynti Kanani, Sandeep Nailwal & Anurag Arjun and launched in 2017.

MATIC holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Polygon’s investors include Coinbase Ventures, ZBS Capital, MiH Ventures, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Polygon

# Polygon Transaction count Methodology

## 1. Overview

The Polygon transaction count metric measures the daily number of unique transactions on the Polygon blockchain, segmented by the destination contract or address. This metric provides insight into network activity and usage patterns by tracking how many distinct transactions are sent to different addresses each day. The calculation counts unique transaction hashes grouped by day and destination address, with enrichment to provide human-readable names for known contracts and addresses.

## 2. Data sources

- **Polygon blockchain transaction records**: Raw transaction data from the Polygon network containing transaction hashes, timestamps, sender and recipient addresses, gas usage, and pricing information
- **Account labeling data**: External data source providing human-readable names and titles for known contract addresses and accounts on Polygon
- **Chain availability configuration**: Data quality metadata that defines time periods where Polygon blockchain data is considered reliable and complete

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract and prepare raw transaction data from Polygon blockchain
- **Logic**: All Polygon blockchain transactions are retrieved with key identifiers and metadata. Each transaction record includes the `block_timestamp`, `transaction_hash`, `from_address`, `to_address`, gas usage metrics, and effective gas pricing. The effective gas price is normalized by dividing by 10^18 to account for 18 decimal place precision. A hardcoded wrapped POL token address (`0x0d500b1d8e8ef31e21c99d1db9a6444d3adf1270`) is assigned as the reference token. All transactions are classified under the 'blockchains_l1' market sector and 'blockchain' business segment with no specific product differentiation.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `to_address` for destination tracking, `gas_used` and `effective_gas_price` for transaction cost metrics

### Component B: Daily transaction aggregation  
- **Purpose**: Group transactions by day and destination address to count unique transactions
- **Logic**: Transaction data is aggregated by truncating timestamps to daily boundaries using `timestamp_trunc`. For each day and destination address (`to_address`), the system counts distinct `transaction_hash` values to avoid counting duplicate transactions. This aggregation maintains the market sector and business segment classifications while preserving the destination address for subsequent enrichment.
- **Key fields**: `timestamp` truncated to day level, `to_address` for grouping, `transaction_count` as the distinct count of transaction hashes

### Component C: Account label enrichment
- **Purpose**: Add human-readable names for known contracts and addresses
- **Logic**: The aggregated transaction data is enriched with account labels through a left join on the `to_address` field. Account labels are sourced from external labeling data filtered specifically for Polygon chain addresses. When a matching label exists, the account's `title` becomes the `contract_name`. For addresses without labels, the system defaults to 'Unlabeled' to ensure all records have a contract name designation.
- **Key fields**: `contract_name` derived from account `title` or defaulted to 'Unlabeled', preserving all existing fields from the aggregation step

### Final aggregation
- **Combining components**: The enriched transaction data flows through a standardization macro that ensures consistent schema structure, validates all required identifiers, and fills any temporal gaps in the data
- **Currency conversion**: Not applicable for this count-based metric
- **Time aggregation**: Data is aggregated at daily granularity with timestamps truncated to day boundaries, maintaining consistent daily partitioning for efficient querying
- **Final calculation**: The final metric represents the count of distinct transaction hashes per day per destination address, enriched with contract names and filtered for data availability periods. Chain availability filtering ensures only reliable data periods are included in the final output.

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

Confirmed transactions added to the blockchain.

PolygonPOL

Transaction count

Transaction count

Competitive landscape

Chain breakdown