# BNB Chain Exchange to Casino Flows | Bitquery Data Store Daily transfers between the hot wallets of 20 exchanges and 53 crypto casino brands on BNB Chain, one row per exchange, casino and day. Dataset page: https://bitquery.io/datastore/datasets/bsc-exchange-casino-flows Network: BNB Chain Category: Transfers, Labels Tables: 1 Columns: 9 Coverage: first block to 2026-11-17 Format: Apache Parquet, ZSTD compression, one prefix per table Licence: https://bitquery.io/datastore/legal/data-license ## What this is Exchange to casino flows are hard to measure from raw transfers, because a player who withdraws from an exchange into a casino pays a one-off deposit address, not a known casino wallet. We find those deposit addresses each month, tie each deposit to a casino brand, and keep the deposits whose sender is an exchange hot wallet. One row is one exchange and one casino on one UTC day, with the number and USD value of transfers in each direction. It covers 1,084 hot wallets of 20 exchanges and 53 casino brands, both from Bitquery's own labels. Most buyers sum deposit_usd by exchange for one casino, or by casino for one exchange. Only exchange hot wallets are matched. A casino payout into a player's exchange deposit address is not counted, so withdrawals are rare in this table, and money a player moves through a personal wallet between the exchange and the casino is not counted either. ## What people use it for - Which exchanges a casino's players withdraw from when they fund an account, by day - Exchange risk reviews: how much leaves an exchange's hot wallets for gambling sites - Choosing which exchanges to support or partner with, from where deposits already come - Casino market share among one exchange's customers on BNB Chain ## Tables (1) ### bsc_exchange_casino_flows: 9 columns Transfers between exchange hot wallets and casinos on BNB Chain, one row per exchange, casino and day. Bucket prefix: bsc/exchange_casino_flows File naming: .parquet, one file per calendar month (ZSTD) Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/bsc/exchange_casino_flows/sample_2026-11-10.parquet Sample updated: Nov 18, 2026 | column | type | description | | --- | --- | --- | | chain | String | bsc | | date | Date | UTC day of the transfers | | exchange | String | Exchange whose hot wallet sent or received the money, from Bitquery labels, e.g. binance, bybit, mexc | | casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame | | deposits | UInt64 | Transfers from the exchange's hot wallets into the casino that day, each worth $1 or more | | deposit_usd | Float64 | USD value of those deposits: USDT and USDC at $1, BNB at the block-time price | | withdrawals | UInt64 | Transfers from the casino's hot wallets to the exchange's hot wallets that day, each worth $1 or more | | withdrawal_usd | Float64 | USD value of those withdrawals, priced the same way | | wallets | UInt64 | Distinct casino-side addresses in the row: deposit addresses and hot wallets that received or sent the money | ## Price - Latest month (Oct 17, 2026 → Nov 17, 2026): $300 one-time, USD - Last 12 months (Nov 17, 2025 → Nov 17, 2026): $3,000 one-time, USD Every window includes all 9 columns. Only the time range changes. ## Questions buyers ask Q: What is in the BNB Chain Exchange to Casino Flows dataset? A: One Parquet table with 9 columns: chain, date, exchange, casino, deposits, deposit USD, withdrawals, withdrawal USD and wallets. One row is one exchange and one casino on one UTC day. Tokens are BNB, USDT and USDC. Q: How big is it? A: Small. A test run for Stake and Stake US on 10 November 2026 gave 8 rows: 7 exchanges paid into Stake and 1 into Stake US. We have not run a full month or all 53 casinos, so there is no month total to quote. Exact row counts and file sizes arrive with the delivery manifest. Q: Which exchanges and casinos are covered? A: 20 exchanges: Binance, OKX, Bybit, Bitget, KuCoin, Gate, MEXC, HTX, Kraken, Coinbase, Crypto.com, BingX, CoinEx, BitMart, LBank, WhiteBIT, Bithumb, XT.com, CoinW and Bitkub, through 1,084 hot wallets in Bitquery's exchange labels. The casinos are the 53 brands of the BNB Chain Casino Player Wallets dataset, including Stake, BC.Game, 1xBet and Roobet. Q: How do I see where a casino's deposits come from? A: Filter casino to the brand and sum deposit_usd by exchange. In the 10 November 2026 test, Binance hot wallets sent 484 deposits worth $85,758.59 to Stake, Bybit 99 worth $39,368.73 and MEXC 51 worth $15,560.30. Q: What share of casino deposits does this capture? A: Only deposits sent straight from an exchange hot wallet. For Stake and Stake US on 10 November 2026 that was 687 of 2,447 deposits and $150,530 of $502,628. The rest came from other wallets, including players' own wallets that may have been funded from an exchange earlier. Q: Why are withdrawals mostly zero? A: A casino pays a player's exchange account through that player's exchange deposit address, and we match exchange hot wallets only. The withdrawals columns count casino transfers that go straight to an exchange hot wallet, which is uncommon. The test day had none. Q: How were the numbers checked? A: We listed every counterparty of Stake and Stake US on 10 November 2026 with a separate query, matched them to the 1,084 exchange wallets offline, and got the same 8 rows as the dataset query, to the cent. That query ran with the 21 exchange wallets active that day; the form with all 1,084 wallets and all 53 casinos has not been run. Q: What limits should I know about? A: Deposit addresses are found per month, so a part-month finds fewer of them and its counts are a lower bound. Exchange labels are a snapshot, and a hot wallet an exchange started using later is missing until the list is refreshed. One hot wallet can serve several products of the same exchange. Q: How do I load it? A: With DuckDB: SELECT exchange, sum(deposit_usd) FROM read_parquet('bsc/exchange_casino_flows/*.parquet') WHERE casino = 'stake' GROUP BY 1 ORDER BY 2 DESC. pandas, Polars, Spark and ClickHouse read the same files. Q: How current is the data and how is it delivered? A: A purchase covers the window up to yesterday, UTC, as flat Parquet files, one file per calendar month, with a JSON manifest listing each file and its sha256. We prepare the files within 7 business days of purchase and email you the location. You choose at checkout between a Requester Pays S3 bucket and a Cloudflare R2 bucket with a read-only API key. Files stay available for 7 days from delivery. Q: Can I try before I buy? A: Yes. The table links to a public sample file with 8 real rows from 10 November 2026, for Stake and Stake US only. ## Data after your purchase A purchase is a one-time set of files, up to the coverage end date on the dataset page. For data after that: - Real-time stream: Kafka Streams sends new BNB Chain data as it happens. Enterprise plan. Topics and schema: https://docs.bitquery.io/docs/streams/kafka-streaming-concepts/#bnb-chain-bsc - Daily warehouse tables: Datashares refreshes tables daily in Snowflake, BigQuery, S3 or Azure. Enterprise plan. https://bitquery.io/products/datashares - Another one-off slice (other chains, tables or dates): a custom extract. https://bitquery.io/products/data-on-demand ## 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.