Indexed PolygonBlockchain Data

Polygon PoS has produced blocks since 2020, when it launched as Matic Network. It runs as two layers rather than one. Heimdall, built on Tendermint, holds the validator set, handles staking and submits periodic checkpoints to Ethereum. Bor produces the EVM blocks users transact on, about one every two seconds, from a producer set Heimdall selects. Validators stake through contracts on Ethereum, but the chain does not publish its transaction data there, only its checkpoints, which is why its blocks cannot be rebuilt from Ethereum the way a rollup’s can. Execution is EVM, with the same bytecode, ABIs and twenty-byte addresses, so contracts move across unchanged. The native gas asset was MATIC until September 2024, when the network migrated to POL at one to one and the ticker changed across the ecosystem. Value bridged in from Ethereum arrives through a state-sync mechanism, so deposits show up as protocol-generated transactions instead of user ones. The zk rollup that shares the brand, Polygon zkEVM, is a separate network whose history is now closed.

SonarX indexes Polygon PoS end to end: blocks and headers, transactions and receipts, event logs decoded against contract ABIs, execution traces including internal value transfers, and token transfers and balances. State-sync transactions and checkpoint records are kept as their own records rather than folded into ordinary transactions. Everything lands in the normalized model SonarX uses across every network it covers, so Polygon joins to its neighbors without a translation layer.

Full historical coverage is available today as a data-share or a file delivery. Real-time delivery keeps the same dataset current to chain tip. Point-in-time balance tables, the real-time balances API and the batch wallets, tokens and balances API are all available for Polygon. Kafka streaming carries the same records as a live topic today.

Two Polygon habits defeat a naive pipeline. Bridged deposits arrive as state-sync transactions generated by the validator set, with no ordinary sender, so anything that keys transfers on a signer misfiles them. And finality is answered on two chains at once: a Bor block is probabilistic until Heimdall’s checkpoint covering it is accepted on Ethereum, and reorgs here have run deeper than Ethereum’s own. Indexed history is corrected against the canonical chain rather than appended to, so a query run twice returns one answer. The 2024 gas-asset migration adds a third wrinkle, because a complete history carries the same asset under two names.

Polygon carries a lot of transfer volume that is not speculative, and the workloads reflect that. Stablecoin and payment analysis is the first: flows between processors, exchanges and end users, reconstructed from token transfers rather than from a payment provider’s own reporting. Token program accounting is the second, covering distributions, vesting contracts and enterprise-issued assets, where the question is who holds what as at a date. NFT sales and gaming economies are the third, since much of that activity moved here for the fee level and stayed. Cross-chain work is routine too, most often against Ethereum, because a bridged asset has a life on both sides and neither half accounts for it alone. DeFi analytics covers the position-level side of this across chains.

Tell us the delivery target, how far back you need and how fresh it has to be, and the share is scoped against that. Polygon history and the balance APIs are available now, so a first delivery is provisioning rather than engineering. The published coverage matrix for every network SonarX indexes lives in the data documentation, and the rest of the catalogue is at all indexed chains.