bsc_casino_player_wallets
12 columnsDeposits and withdrawals per wallet and casino on BNB Chain, one row per wallet, casino and month.
bsc/casino_player_wallets<YYYY-MM>.parquetone file per calendar month (ZSTD)Monthly deposits and withdrawals of each wallet at 53 crypto casino brands on BNB Chain, one row per wallet, casino and month.
bsc_casino_player_walletsBNB Chain casino player wallets are hard to list from raw transfers, because most casinos give each player a deposit address that forwards the money to a hot wallet. We find those deposit addresses each month, tie every deposit and withdrawal to a casino brand, and roll the transfers up to the wallet that paid or was paid. One row is one wallet at one casino in one calendar month, with the number and USD value of its deposits and withdrawals, the days it was active and how many casinos it paid into. It covers 53 brands, from 114 hot wallets in Bitquery's own gambling labels.
Most buyers start by ranking wallets: filter casino to a brand, keep deposits above 0 and sort by deposit_usd. A casino sees only what a player deposits with it, so the rows for the same wallet at other brands show what it spends elsewhere. A wallet is not always one player. Exchange and payment-service wallets pay casino deposit addresses for many customers, and they show up with thousands of deposits or a high casinos_used.
Deposits and withdrawals per wallet and casino on BNB Chain, one row per wallet, casino and month.
bsc/casino_player_wallets<YYYY-MM>.parquetone file per calendar month (ZSTD)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.
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# bsc_casino_player_wallets: one file per calendar month (ZSTD)
bsc/casino_player_wallets<YYYY-MM>.parquetEvery window includes 12 columns. Only the time range changes.
bsc_casino_player_wallets table, 12 columnsOne Parquet table with 12 columns: chain, month, wallet, casino, deposits, deposit USD, withdrawals, withdrawal USD, active days, first and last time, and casinos used. One row is one wallet at one casino in one calendar month. Tokens are BNB, USDT and USDC.
We have not run a full month yet, so there is no month total to quote. A test run for Stake and Stake US on 10 November 2026 gave 1,192 rows for 1,182 wallets, with 2,447 deposits worth $502,628. Exact row counts and file sizes arrive with the delivery manifest.
53 brands owned by 50 companies, including Stake, Stake US, BC.Game, 1xBet, Duelbits, Roobet, Rollbit and Rainbet. The list comes from 114 hot wallets in Bitquery's gambling labels, with payment processors removed. Ethereum, Tron and Solana are in the Crypto Casino Player Wallets dataset.
Take the wallets that deposit at your brand, then sum deposit_usd for the same wallets at every other casino. A wallet with a small deposit at one brand and large deposits elsewhere is a candidate for a VIP review. casinos_used gives the number of brands it paid into that month.
No. The wallet is whoever sent the deposit or received the withdrawal. When a player deposits straight from an exchange, the wallet is the exchange's hot wallet, and it carries many players' deposits. Rows with deposits of 0 are wallets that only received money from a casino, which includes moves to exchanges.
A wallet counts as a casino's deposit address in a month when it forwards 80 to 125 percent of what it receives to that brand's hot wallets and has at most 50 senders. Every transfer into it is then a deposit by the sender. Payments straight to a hot wallet count as deposits too. USDT and USDC are matched by contract, BNB counts as top-level value only, and transfers under $1 are left out.
The query ran for Stake and Stake US on 10 November 2026 and returned the 12 columns with the listed types. The same roll-up on Ethereum matched a separate count of Shuffle's hot wallet transfers for 10 to 12 November: 3,894 withdrawals against 3,911, where the 17 extra are moves into Shuffle's own deposit addresses. No full month and no run with all 53 brands has been done on BNB Chain yet.
Deposit addresses are found per month, so a part-month finds fewer of them and its deposit counts are a lower bound. That applies to the first and last month of a purchase and to the sample file. casinos_used counts BNB Chain only, and the same person can use different wallets on other chains. A transfer from one casino's hot wallet into another casino's deposit address counts as a deposit by that hot wallet.
With DuckDB: SELECT wallet, sum(deposit_usd) FROM read_parquet('bsc/casino_player_wallets/*.parquet') WHERE casino = 'stake' GROUP BY 1 ORDER BY 2 DESC LIMIT 100. pandas, Polars, Spark and ClickHouse read the same files.
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.
Yes. The table links to a public sample file with 50 real rows from 10 November 2026, for Stake and Stake US only. It covers one day, not a month, so it finds fewer deposit addresses than a full month does.
192.6 million address labels on 38 chains, from exchange deposit and hot wallets to casinos, mixers, darknet markets, scams and sanctioned addresses.
Every bonding-curve trade, token creation, migration and pool on Pump.fun, plus per-token OHLCV, decoded and USD-priced.
Every TRX, TRC-10 and TRC-20 transfer on TRON since June 2018, one row per transfer, valued in USD where a price exists.
Tell us the chain, tables and date range.