# Polygon Transfers — Bitquery Data Store

Every native POL and token transfer on Polygon since May 2020, one row per transfer, valued in USD where a price exists.

Dataset page: https://bitquery.io/datastore/datasets/polygon-transfers
Network: Polygon
Category: Transfers
Tables: 1
Columns: 24
Coverage: 2020-05-30 to 2026-09-24
Refresh: Daily
Rows: about 29B
Size: about 780 GB
Format: Apache Parquet, Snappy compression, one prefix per table
Licence: https://bitquery.io/datastore/legal/data-license

## What this is

We decode Polygon transfers from the chain ourselves: token transfer events, plus native POL including what contracts move in internal calls. Each row carries the token's name, symbol and exact decimals, and a USD value for POL and the five other assets our hourly series covers on Polygon. About 28.7 billion rows, from block 447 on 30 May 2020 to yesterday.

Most buyers start with flow for one token: filter Transfer_Currency_SmartContract to its contract, then group by sender and receiver. Filter Transfer_Currency_Native instead to see POL moving on its own. Amounts are decimal strings, so cast with care, and join on contract addresses because symbols repeat.

## What people use it for

- Token flow analysis for any contract on Polygon
- Token balance history for any address, rebuilt from its transfers
- Exchange deposit and withdrawal attribution
- Native POL movement separated from token movement

## Tables (1)

### transfers — 24 columns

One row per native POL or token transfer on Polygon, with sender, receiver, token metadata and a USD value where a price exists.

S3 prefix: matic/transfers
File naming: <start_block>_<end_block>.parquet, 50 blocks per file, sorted ascending
Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/matic/transfers/82133800_82133849.parquet
Sample updated: Feb 13, 2026

| column | type | description |
| --- | --- | --- |
| Block_Date | Date | UTC date of the block |
| Block_Number | UInt64 | Block height |
| Block_Time | DateTime | Block timestamp, UTC |
| Fee_SenderFee | String | Network fee the sender paid for the whole transaction, in POL, as a decimal string. It repeats on every row of the transaction, so count it once per transaction |
| Transaction_Hash | String | Hash of the transaction this row settled in, 0x-prefixed; the join key to transactions and logs |
| Transaction_Index | UInt64 | Position of the transaction within the block |
| TransactionStatus_Success | String | Whether the transaction succeeded; the string true or false. Failed transactions are kept |
| Transaction_Type | UInt32 | EIP-2718 transaction type: 0 legacy, 1 access list, 2 EIP-1559, 4 EIP-7702 |
| Transfer_Amount | String | Amount moved, decimal adjusted, as a decimal string with exactly as many places as the token has decimals. Multiply by 10 to the power of the decimals for the raw on-chain integer |
| Transfer_AmountInUSD | Float64 | Amount valued in USD at the hourly price for the block's hour; 0 when the amount is 0 or the token has no price |
| Transfer_Currency_Decimals | Int32 | Decimals of the transferred currency, as its contract reports them |
| Transfer_Currency_DelegatedTo | String | Implementation address for proxy tokens; the string 0x when there is none |
| Transfer_Currency_Fungible | String | Whether the currency is fungible; the string true or false, and false for NFTs |
| Transfer_Currency_Name | String | Name reported by the contract; lookalike tokens copy real names |
| Transfer_Currency_Native | String | true for native POL, false for tokens. Native rows still carry the old symbol MATIC; filter on this column to find them |
| Transfer_Currency_ProtocolName | String | Token standard, for example erc20 or erc721; empty for native POL |
| Transfer_Currency_SmartContract | String | Contract of the transferred token, 0x-prefixed; the string 0x for native POL |
| Transfer_Currency_Symbol | String | Symbol reported by the contract; repeats across tokens, so join on the contract address |
| Transfer_Id | String | Token id for NFT transfers; the string 0 for fungible transfers |
| Transfer_Index | UInt32 | Position within the transaction. Several rows in one transaction can share it |
| Transfer_Sender | String | Sending address, 0x-prefixed |
| Transfer_Receiver | String | Receiving address, 0x-prefixed |
| Transfer_Type | String | token for token transfers and call for every native POL movement, a plain send included; Polygon files never use transaction |
| Transfer_URI | String | Metadata URI for NFT transfers; empty otherwise |

## Price

- Latest month (Aug 24, 2026 → Sep 24, 2026): $300 one-time, USD
- Last 12 months (Sep 24, 2025 → Sep 24, 2026): $1,800 one-time, USD
- Last 24 months (Sep 24, 2024 → Sep 24, 2026): $3,600 one-time, USD
- Full history (May 30, 2020 → Sep 24, 2026): $9,000 one-time, USD

Every window includes all 24 columns. Only the time range changes.

## Questions buyers ask

Q: What is in the Polygon Transfers dataset?
A: One Parquet table with 24 columns: every native POL and token transfer on Polygon, one row each, with the amount, the token's details, the transaction it settled in and the fee. POL moved by contracts in internal calls is included, and so are NFTs.

Q: How big is it?
A: About 28.7 billion rows over 77 months, roughly 780 GB as Parquet, estimated from the sample files. The last 24 months hold about 19.3 billion rows and the last 12 months about 15.0 billion. Row counts come from the live table; exact figures arrive with the delivery manifest.

Q: How far back does it go?
A: To the start of indexed history: from 30 May 2020, at block 447, the first block with a transfer. The Full window runs from there to yesterday.

Q: What was left out, and why?
A: The export applies no filter of its own: spam tokens, lookalike tokens, zero-value rows and failed transactions all stay in, and the columns let you drop them. Value credited outside a transaction or a contract call has no row, the genesis allocation for one, so check native POL balances rebuilt from these rows against the chain. Token balances hold, rebasing tokens aside.

Q: How are amounts valued in USD?
A: Only six currencies have a price history on Polygon: POL (formerly MATIC), WPOL, WETH, USDT, DAI and the bridged USDC.e. Circle's native USDC has no series yet. In a recent six-hour window that priced about 22% of rows; the rest is mostly airdrop and spam tokens. The free sample was priced from a wider short-term source, so half its rows show a USD value, more than a delivered file will. A value of 0 means either a $0 transfer or no price; the column cannot tell them apart.

Q: How are these produced, and how were they checked?
A: Decoded from Polygon by our own indexer, which reads token transfer events and traces internal calls for POL. Before release we read the sample back: 34,525 rows over blocks 82,133,800 to 82,133,849, every amount carrying exactly its token's decimals. The live table returns the same 34,525 rows for those blocks.

Q: Where is the raw integer amount?
A: The amount column is decimal adjusted. Multiply it by 10 to the power of the token's decimals for the raw on-chain integer. We ship the adjusted value because decimals differ per token and the raw figure is wrong without them.

Q: What should I watch out for?
A: Amounts are decimal strings, so casting to float loses precision on large values. Symbols and names repeat, and lookalike tokens copy them, so join on the contract address. Failed transactions are kept; filter TransactionStatus_Success for settled flow. Zero-value rows, 0.3% of the sample, move nothing, so drop them before counting activity. Every native POL row is marked call in Transfer_Type, a plain send included. The S3 prefix is matic/transfers, the chain's name before the rebrand to POL.

Q: How do I get one token, or native coin only?
A: Filter Transfer_Currency_SmartContract to the token's contract, lower case with 0x. For native POL alone, filter Transfer_Currency_Native to true; its contract column holds the string 0x. The files still label native rows MATIC, so a filter on the symbol POL finds nothing.

Q: How do I load it?
A: One line in DuckDB: SELECT * FROM read_parquet('transfers/*.parquet') LIMIT 10. Pandas works too: pandas.read_parquet(path). The sample file opens without credentials.

Q: How current is it, and how is it delivered?
A: Refreshed daily with T+1 latency, so a purchase made today includes everything to yesterday. Delivered as Parquet named by block range, 50 blocks per file and sorted ascending, under a stable S3 layout with a JSON manifest listing every file and its sha256. Signed HTTPS links are emailed once the files are prepared, or on request we deliver into your own S3, GCS or R2 bucket.

## What this file is, and is not

This is a description of one dataset sold by Bitquery, written for assistants and for people. It lists every column, but holds no data rows — the sample files linked under each table are real Parquet and are free to download. Figures here come from the product record and are exact unless marked otherwise; the delivery manifest is authoritative for a purchased file. If a question needs a row that is not in a sample, say so rather than guessing at it.