TL;DR Short answer: Polygon ETL tools move on-chain data from the Polygon PoS blockchain, such as blocks, transactions, logs, token transfers and contract events, into a warehouse for blockchain analytics. Google BigQuery offers Polygon public datasets you can query with SQL, Dune and Goldsky provide decoded and streamed chain data, Polygonscan's data is available through Etherscan API V2, and Airbyte's Connector Builder or dlt can pull from those APIs or RPC nodes. Eight Polygon ETL tools compared:
Airbyte Google BigQuery public datasets Etherscan API V2 (Polygonscan) Dune Goldsky The Graph RPC node providers dlt The Polygon constraint: Polygon PoS produces blocks roughly every two seconds, so full history is very large, and raw logs need decoding with contract ABIs before they mean anything; most teams start from decoded or pre-indexed data rather than raw RPC. Polygon ETL tools extract on-chain data from Polygon, the Ethereum-aligned blockchain network whose main chain is Polygon PoS, and load it into a warehouse. Teams use the data to track protocol usage and revenue, wallet behaviour, token flows, NFT activity and gas costs, and to join on-chain activity with off-chain product and finance data. If you are looking for the Polygon.io market data API, now called Massive, see our guide to Polygon.io stock data ETL tools .
What is the Polygon blockchain, and what changed with POL? Polygon is a network of Ethereum-compatible chains, and its main chain, Polygon PoS, is an EVM chain with chain ID 137. Several changes affect data pipelines:
MATIC to POL: in September 2024 the native token migrated from MATIC to POL, which is now used for gas and staking, so historical analysis spans both tickers.Polygon zkEVM: Polygon Labs announced in 2025 that it would sunset the zkEVM Mainnet Beta, so most new data work focuses on Polygon PoS.Agglayer: Polygon's cross-chain interoperability layer connects multiple chains, which makes cross-chain flows part of the picture.EVM compatibility: Polygon PoS uses the same data model as Ethereum, with blocks, transactions, receipts, logs and traces, so Ethereum tooling largely works unchanged.Every Polygon ETL tool works from the same on-chain building blocks:
Blocks: block number, timestamp, gas used and producer.Transactions: sender, recipient, value, gas price, input data and status.Logs and events: contract events such as ERC-20 transfers, swaps and mints, which need ABI decoding.Token transfers: ERC-20, ERC-721 and ERC-1155 movements derived from logs.Traces: internal calls between contracts, available from some providers.Contracts and balances: contract metadata, verified source and wallet balances.How do the Polygon ETL tools compare? Tool Approach Data Best for Cost Airbyte Connector Builder on APIs or RPC Whatever you configure On-chain data next to off-chain sources Free self-hosted Core; paid Cloud plans BigQuery datasets Public datasets in BigQuery Blocks, transactions, logs SQL analysis without running nodes BigQuery query charges beyond the free tier Etherscan API V2 Explorer API Transactions, transfers, balances, contracts Wallet and contract lookups Free tier, then paid plans Dune Decoded SQL platform Decoded protocol tables Protocol analytics and dashboards Free tier, then paid plans Goldsky Indexing and streaming Raw or decoded data into your database Production pipelines into your own stack Usage-based plans The Graph Subgraphs over GraphQL Contract-specific indexed data Application-specific queries Query fees on the network; free studio allowance RPC providers JSON-RPC Raw blocks, receipts, logs and traces Full control and custom decoding Free tiers, then usage-based plans dlt Python loader Any API or RPC data Python teams loading a warehouse Free, open source
Which Polygon ETL tools should you consider? Eight Polygon ETL tools, from public datasets to streaming pipelines:
1. Airbyte Airbyte is the open-source data connectivity platform for AI and analytics. It does not have a dedicated Polygon blockchain connector, so among Polygon ETL tools Airbyte works through the no-code Connector Builder: you configure Etherscan API V2 endpoints, such as transactions and token transfers by address with a start block, or an RPC provider's API, and sync the results incrementally. For other ELT options, see our guide to ELT tools .
That puts on-chain activity next to product, CRM, payments and market data from 700+ connectors, which is where on-chain analytics meets the rest of the business. Airbyte runs in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Key features Connector Builder: configure API key authentication, pagination and block-based cursors.Incremental syncs: use block numbers as cursors for new activity.Multi-chain: the same Etherscan V2 source works for other EVM chains by changing the chain ID.Any destination: BigQuery, Snowflake, ClickHouse, Postgres and more.Best for: teams tracking specific wallets or contracts alongside off-chain business data.
Pricing: self-hosted Airbyte Core is free; Airbyte Cloud is billed on volume, and Pro and Airbyte Flex on capacity.
Pros Cons Custom Polygon source with no code No dedicated Polygon connector On-chain next to off-chain data Better for targeted addresses than full chain history Cloud, Flex or self-hosted Core Decoding logs needs contract ABIs
2. Google BigQuery public datasets Google has hosted Polygon blockchain data as a BigQuery public dataset since 2021, and its Blockchain Analytics programme publishes a Polygon mainnet dataset with blocks, transactions and logs, where addresses are stored in lowercase. Queries count against BigQuery's free monthly processing allowance, which makes it the fastest way to start among Polygon ETL tools, though you should check Google's documentation for the current status of each Polygon listing. For BigQuery tooling, see our guide to BigQuery ETL tools .
Key features Core tables: blocks, transactions and logs.Cross-chain queries: combine Polygon with other public blockchain datasets.SQL: query with standard BigQuery SQL.Joins: combine with your own data loaded into BigQuery.Best for: analysts who want Polygon data in SQL without infrastructure.
Pricing: BigQuery storage and query charges beyond the free monthly allowance.
Pros Cons No nodes or pipelines to run Raw data still needs decoding Standard SQL across chains Check current listing status in Google's docs Free monthly processing allowance Large scans cost money beyond the free tier
3. Etherscan API V2 (Polygonscan) Among Polygon ETL tools for targeted lookups, Polygonscan, the main Polygon PoS block explorer, is run by the Etherscan team, and its API is now served through Etherscan API V2: one API key works across more than 60 EVM chains, and you pass chain ID 137 for Polygon mainnet or 80002 for the Amoy testnet. It is the simplest way to pull transactions, token transfers, balances and verified contract data for specific addresses.
Key features Accounts: transactions, internal transactions and token transfers by address.Contracts: verified source code and ABIs.Logs: event logs filtered by address and topic.Gas and stats: gas prices and network statistics.Best for: teams tracking specific wallets, contracts or tokens.
Pricing: a free tier with rate limits, then paid plans for higher limits.
Pros Cons One key for 60+ chains Rate limits on free plans Decoded token transfers Address-centric rather than full-chain Verified contract source and ABIs Paid plans for higher throughput
4. Dune Dune is a SQL analytics platform over decoded blockchain data, including Polygon, with community-built tables for protocols, tokens and NFTs. Its API returns query results programmatically, and its data sharing options can deliver tables into warehouses such as Snowflake and BigQuery. For crypto market data to join with, see our guide to CoinGecko ETL tools .
Key features Decoded tables: protocol, token and NFT tables built by the community.SQL editor: query and visualise in the browser.API: execute queries and fetch results programmatically.Data sharing: deliver datasets into warehouses.Best for: analysts and protocol teams who want decoded data fast.
Pricing: a free tier for exploration, then paid plans for API and higher limits.
Pros Cons Decoded, community-curated tables Data lives in Dune unless exported Fast dashboards and SQL API and data sharing on paid plans Broad multi-chain coverage Less control over transformation logic
5. Goldsky Goldsky is one of the production-grade Polygon ETL tools: it indexes blockchain data and streams it into infrastructure you control, with pipelines that deliver raw or decoded Polygon data into databases such as Postgres and ClickHouse, warehouses, Kafka or object storage, and it also hosts subgraphs. It suits teams that want low-latency chain data in their own stack.
Key features Streaming pipelines: deliver chain data continuously into your destinations.Subgraph hosting: run subgraphs with managed infrastructure.Decoding: decode events into structured tables.Many destinations: Postgres, ClickHouse, Kafka, S3 and warehouses.Best for: engineering teams running on-chain data in production.
Pricing: usage-based plans; check current pricing.
Pros Cons Streams into your own database Usage-based costs grow with volume Raw and decoded data Another vendor in the pipeline Low latency Configuration needs care for reorgs
6. The Graph The Graph lets developers define subgraphs that index specific contracts and events on Polygon and other chains, then query the results over GraphQL. It is ideal for application-specific data, such as a single protocol's pools or positions, rather than full-chain analytics. For API-based pipelines, see our guide to REST API ETL tools .
Key features Subgraphs: define entities and event handlers for specific contracts.GraphQL: query indexed data with flexible filters.Existing subgraphs: reuse community subgraphs for popular protocols.Subgraph Studio: build and test subgraphs before publishing.Best for: application teams that need indexed data for specific protocols.
Pricing: query fees on the decentralised network, with a free monthly allowance in Subgraph Studio.
Pros Cons Indexes exactly the contracts you need Not built for full-chain analytics GraphQL queries Subgraphs need writing and maintaining Large ecosystem of existing subgraphs Query fees on the decentralised network
7. RPC node providers At the lowest level of Polygon ETL tools, providers such as Alchemy, QuickNode and Infura offer managed JSON-RPC endpoints for Polygon PoS, giving raw access to blocks, transactions, receipts, logs and, on some plans, traces. Running your own Bor node is also possible. RPC gives full control but leaves decoding, reorg handling and scaling to you.
Key features JSON-RPC: standard Ethereum methods such as eth_getBlockByNumber and eth_getLogs.Archive access: historical state on archive plans.Traces: internal calls on supported plans.WebSockets: subscribe to new blocks and logs.Best for: teams building custom indexers or needing raw data.
Pricing: free tiers for light use, then usage-based plans.
Pros Cons Raw, complete data Decoding and indexing are yours to build Managed providers remove node operations eth_getLogs block-range limits Traces and archive data on some plans Costs grow with request volume
8. dlt dlt is one of the code-first Polygon ETL tools: an open-source Python library that can page through Etherscan API V2 or call RPC methods, then load the results into DuckDB, BigQuery, Snowflake or ClickHouse, using block numbers for incremental loads. For more code-first options, see our guide to Python ETL tools .
Key features REST API source: page through explorer endpoints.Custom resources: wrap RPC calls in Python generators.Incremental: resume from the last processed block.Many destinations: DuckDB locally, warehouses in production.Best for: Python teams building targeted Polygon pipelines.
Pricing: free and open source under the Apache 2.0 licence; you pay for where it runs.
Pros Cons Incremental loading on block numbers You write and schedule the pipeline Works with APIs or RPC Decoding logic is yours Free and open source Rate limits are yours to handle
Polygonscan, RPC nodes or indexers: where should Polygon data come from? The right source depends on the question you are answering:
Explorer API (Polygonscan): best for specific wallets, contracts and tokens, with decoded transfers and verified ABIs.Public datasets and Dune: best for SQL analysis across the whole chain without running infrastructure.Indexers (Goldsky, The Graph): best for production applications that need specific, low-latency indexed data.RPC nodes: best when you need raw data, traces or custom decoding that other sources do not offer.Combining sources: many teams use public datasets for history and APIs or streams for fresh data.For market prices to join with on-chain activity, see our guide to CoinMarketCap ETL tools .
What should you check before syncing Polygon data? Whichever Polygon ETL tools you choose, check these first:
Scope: decide between targeted addresses and full-chain history, since full history is very large.Decoding: collect contract ABIs so logs become readable events.Reorgs and finality: recent blocks can be reorganised, so wait for finality or reprocess recent blocks.Address formats: normalise addresses to lowercase before joining sources.Token decimals: divide raw token amounts by each token's decimals, and track MATIC and POL separately in historical data.Rate limits: free API and RPC tiers throttle requests, so plan batch sizes and back-off.How do you start pulling Polygon data with Airbyte? If you decide to test Airbyte, setting up a Polygon pipeline takes three steps.
Step 1: Get an Etherscan API key Create an Etherscan account and API key, which works for Polygon PoS with chain ID 137.
Step 2: Build a Polygon source in the Connector Builder In Airbyte, open the Connector Builder and create streams for transactions and token transfers for the addresses you track, with the API key, chain ID 137 and a start-block cursor for incremental syncs. Test it, then publish it to your workspace.
Step 3: Set up a destination and connection Pick a destination, such as BigQuery, Snowflake or ClickHouse, and schedule syncs. The process is the same whether you start with Airbyte Cloud or run self-hosted Airbyte Core .
Which Polygon ETL tool should you choose? Choosing between Polygon ETL tools depends on scope and freshness. For SQL over the whole chain, start with BigQuery public datasets or Dune. For production pipelines into your own stack, use Goldsky, or RPC providers if you need raw data and custom decoding. For specific wallets and contracts next to off-chain data, build on Etherscan API V2 with Airbyte's Connector Builder or dlt, and use The Graph for application-specific indexing. For analytical databases suited to chain data, see our guide to ClickHouse ETL tools .
Combine Polygon on-chain data with Airbyte Build a Polygon source with the Connector Builder and sync on-chain activity next to product, payments and market data from 700+ sources, in Airbyte Cloud, in your own environment with Airbyte Flex, or self-hosted with Airbyte Core.
Try Airbyte Cloud free for 14 days or talk to our team .
Frequently Asked Questions (FAQs) 1. What are the best Polygon ETL tools? Google BigQuery public datasets and Dune suit SQL analysis, Goldsky and RPC providers suit production pipelines, and Etherscan API V2 suits wallet and contract lookups. Airbyte's Connector Builder and dlt can load API or RPC data next to off-chain sources, and The Graph indexes specific contracts.
2. Does Airbyte have a Polygon blockchain connector? Airbyte does not have a dedicated Polygon blockchain connector. You can build one with the no-code Connector Builder on Etherscan API V2 or an RPC provider's API.
3. Is the Polygonscan API still available? Polygonscan's data is now served through Etherscan API V2, which uses one API key across more than 60 EVM chains; pass chain ID 137 for Polygon PoS.
4. What happened to MATIC? In September 2024, Polygon's native token migrated from MATIC to POL, which is now used for gas and staking on Polygon PoS.
5. Is this page about Polygon.io? No. This page covers the Polygon blockchain. Polygon.io, the market data API now called Massive, is covered in our Polygon.io stock data guide.
Suggested reads Polygon.io Stock Data ETL Tools
CoinGecko ETL Tools
CoinMarketCap ETL Tools
BigQuery ETL Tools
