transfers
24 columnsOne row per native BNB or token transfer on BSC, with sender, receiver, token metadata and a USD value where a price exists.
bsc/transfers<start_block>_<end_block>.parquet50 blocks per file, sorted ascendingBBNB ChainTransfers
BSC Transfers
Every native BNB and token transfer on BSC, one row per transfer, with sender, receiver and a USD value where a price exists.
- Coverage
- Aug 29, 2020→ Sep 24, 2026 · yesterday
- Rows
- ≈41Brows · estimate
- Table
- 1
transfers - Columns
- 24typed
Coverage ends yesterday, UTC
Overview
This is every transfer on BSC, native BNB and tokens alike, from 29 August 2020. Each row names the sender, the receiver, the token with its decimals and symbol, and the transaction it settled in. 40.7 billion rows in all.
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 BNB moving on its own. Amounts are decimal strings, so cast with care, and join on contract addresses rather than symbols, which repeat.
Use cases
- Token flow analysis for any contract on BSC
- Address-level balance reconstruction at any block
- Exchange deposit and withdrawal attribution
- Native BNB movement separated from token movement
Table
Schema reference
ColumnTypeDescription
Block3
Block_DateDateUTC date of the block
Block_NumberUInt64Block height
Block_TimeDateTimeBlock timestamp, UTC
Fee1
Fee_SenderFeeStringNetwork fee the sender paid for the whole transaction, in BNB, as a decimal string. It repeats on every transfer in the transaction, so sum it per transaction, not per row
Transaction3
Transaction_HashStringHash of the transaction this transfer settled in, 0x-prefixed; the join key to transactions and logs
Transaction_IndexUInt64Position of the transaction within the block
Transaction_TypeUInt64EIP-2718 transaction type: 0 legacy, 2 EIP-1559, 4 EIP-7702
TransactionStatus1
TransactionStatus_SuccessStringWhether the transaction succeeded; the string true or false. Failed transactions are kept
Transfer16
Transfer_AmountStringAmount transferred, decimal adjusted, as a decimal string with exactly Transfer_Currency_Decimals places. Multiply by 10^Transfer_Currency_Decimals for the raw on-chain integer
Transfer_AmountInUSDFloat64Amount 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_DecimalsInt64Decimals of the transferred currency, as its contract reports them
Transfer_Currency_DelegatedToStringImplementation address for proxy tokens; the string 0x when there is none
Transfer_Currency_FungibleStringWhether the currency is fungible; the string true or false, and false for NFTs
Transfer_Currency_NameStringName reported by the contract; lookalike tokens copy real names
Transfer_Currency_NativeStringtrue for native BNB, false for tokens. Filter on this to separate base-asset flow from token flow
Transfer_Currency_ProtocolNameStringToken standard, for example erc20 or erc721; empty for native BNB
Transfer_Currency_SmartContractStringContract of the transferred token, 0x-prefixed; the string 0x for native BNB
Transfer_Currency_SymbolStringSymbol reported by the contract; repeats across tokens, so join on the contract address
Transfer_IdStringToken id for NFT transfers; the string 0 for fungible transfers, not empty
Transfer_IndexUInt64Transfer index within the transaction. Not unique: several transfers in one transaction can share it
Transfer_SenderStringSending address, 0x-prefixed
Transfer_ReceiverStringReceiving address, 0x-prefixed
Transfer_TypeStringtoken for token transfers, transaction for a transaction's own value, call for BNB moved by an internal call
Transfer_URIStringMetadata URI for NFT transfers; empty otherwise
Ask an AI about this data
Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Delivery
Parquet files, delivered as signed download links by email after payment, in this layout:
# transfers — 50 blocks per file, sorted ascending
bsc/transfers<start_block>_<end_block>.parquet- Download a free sampleNo email needed.
- Pay nowName, work email and licence check.
- Pay the invoiceBy card or bank transfer.
- Get signed linksThe team prepares the export and emails the links.
Time windows
Every window includes 24 columns. Only the time range changes.
In every window
- The
transferstable, 24 columns - Parquet files in the layout under Delivery
- Signed download links by email
- Licensed under the Data License
FAQ
What is in the BSC Transfers dataset?
One Parquet table with 24 columns: every native BNB and token transfer on BSC, one row each, with sender, receiver, amount, token metadata, the transaction it settled in and the fee. Internal transfers of BNB made by contract calls are included.
How big is it?
About 40.7 billion rows and 3.35 TiB across 74 monthly partitions. The last 24 months hold about 27.6 billion of them and the last 12 months about 19.0 billion. Figures are approximate until the delivery manifest is generated.
How far back does it go?
To the start of indexed history: from 29 August 2020, the week the chain started, at block 363. The Full window runs from there to yesterday.
How are amounts valued in USD?
Prices come from BSC's own hourly series, which carries about 1,600 tokens. In the published sample 82% of rows have a USD value; the rest are zero-value transfers and tokens with no market, which is correct. A value of 0 means either a $0 transfer or no price; the column cannot tell them apart.
Where is the raw integer amount?
Transfer_Amount is decimal adjusted. Multiply it by 10 to the power of Transfer_Currency_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.
What should I watch out for?
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, so filter TransactionStatus_Success for settled flow. Zero-value transfers are common: they are address-poisoning attempts, not real movement. USDT on BSC has 18 decimals, not 6 as on Ethereum and TRON, so check Transfer_Currency_Decimals before comparing amounts across chains.
How do I get one token, or native coin only?
Filter Transfer_Currency_SmartContract to the token's contract, lower case with 0x. For native BNB alone, filter Transfer_Currency_Native to true; its contract column holds the string 0x.
How do I load it?
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.
How current is it, and how is it delivered?
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.
Related datasets
All datasetsSSolanaLast 12 months
Pump.fun
Every bonding-curve trade, token creation, migration and pool on Pump.fun, plus per-token OHLCV, decoded and USD-priced.
TradesPoolsTransfers
- Tables
- 4
- Columns
- 137
- From
- $300
TTronFull history
TRON Transfers
Every TRX, TRC-10 and TRC-20 transfer on TRON since mainnet launch in June 2018, one row per transfer, valued in USD at block time.
Transfers
- Tables
- 1
- Rows
- ≈13B
- From
- $200
EEthereumFull history · daily
Ethereum Transfers
Every native ETH and token transfer on Ethereum since August 2015, one row per transfer, valued in USD where a price exists.
Transfers
- Tables
- 1
- Rows
- ≈7.5B
- From
- $250
Need a custom window, extra tables or CSV?
Tell us the chain, tables and date range.