# Crypto Casino Player Wallets | Bitquery Data Store Monthly deposits and withdrawals of each wallet at 91 crypto casino brands on Ethereum, Tron and Solana, one row per wallet, casino and month. Dataset page: https://bitquery.io/datastore/datasets/casino-player-wallets Network: Multi-chain Category: Transfers, Labels Tables: 3 Columns: 36 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 Crypto 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 91 brands on Ethereum, Tron and Solana, from Bitquery's own gambling hot-wallet labels. Most buyers start by ranking wallets: filter casino to a brand, keep deposits above 0 and sort by deposit_usd. 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. Join the Address Labels dataset on wallet to remove them, or cap deposits and casinos_used. ## What people use it for - Lists of wallets that deposit at a rival brand, ranked by monthly deposit value - High-roller lists: wallets above a deposit threshold at one casino or across several - Player overlap between two brands, from wallets that paid into both in the same month - Retention by month: which wallets that deposited last month deposited again ## Tables (3) ### ethereum_casino_player_wallets: 12 columns Deposits and withdrawals per wallet and casino on Ethereum, one row per wallet, casino and month. Bucket prefix: ethereum/casino_player_wallets 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/ethereum/casino_player_wallets/sample_2026-11-10_2026-11-12.parquet Sample updated: Nov 18, 2026 | column | type | description | | --- | --- | --- | | chain | String | ethereum, tron or solana | | month | Date | First day of the calendar month the row covers, UTC | | wallet | String | Wallet that paid into the casino or was paid by it (owner wallet on Solana) | | casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame | | deposits | UInt64 | Transfers this wallet paid into the casino in the month, each worth $1 or more | | deposit_usd | Float64 | USD value of those deposits: stablecoins at $1, native coin at the block-time or hourly price | | withdrawals | UInt64 | Transfers the casino's hot wallets paid to this wallet in the month, each worth $1 or more | | withdrawal_usd | Float64 | USD value of those withdrawals, priced the same way | | active_days | UInt32 | UTC days in the month with at least one deposit or withdrawal between this wallet and this casino | | first_time | DateTime | Block time of the first deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | last_time | DateTime | Block time of the last deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | casinos_used | UInt32 | Casinos on this chain that the wallet paid into in the month; 0 when it only received withdrawals | ### tron_casino_player_wallets: 12 columns Deposits and withdrawals per wallet and casino on Tron, one row per wallet, casino and month. Bucket prefix: tron/casino_player_wallets 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/tron/casino_player_wallets/sample_2026-11-10.parquet Sample updated: Nov 18, 2026 | column | type | description | | --- | --- | --- | | chain | String | ethereum, tron or solana | | month | Date | First day of the calendar month the row covers, UTC | | wallet | String | Wallet that paid into the casino or was paid by it (owner wallet on Solana) | | casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame | | deposits | UInt64 | Transfers this wallet paid into the casino in the month, each worth $1 or more | | deposit_usd | Float64 | USD value of those deposits: stablecoins at $1, native coin at the block-time or hourly price | | withdrawals | UInt64 | Transfers the casino's hot wallets paid to this wallet in the month, each worth $1 or more | | withdrawal_usd | Float64 | USD value of those withdrawals, priced the same way | | active_days | UInt32 | UTC days in the month with at least one deposit or withdrawal between this wallet and this casino | | first_time | DateTime | Block time of the first deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | last_time | DateTime | Block time of the last deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | casinos_used | UInt32 | Casinos on this chain that the wallet paid into in the month; 0 when it only received withdrawals | ### solana_casino_player_wallets: 12 columns Deposits and withdrawals per wallet and casino on Solana, one row per wallet, casino and month. Bucket prefix: solana/casino_player_wallets 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/solana/casino_player_wallets/sample_2026-11-10.parquet Sample updated: Nov 18, 2026 | column | type | description | | --- | --- | --- | | chain | String | ethereum, tron or solana | | month | Date | First day of the calendar month the row covers, UTC | | wallet | String | Wallet that paid into the casino or was paid by it (owner wallet on Solana) | | casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame | | deposits | UInt64 | Transfers this wallet paid into the casino in the month, each worth $1 or more | | deposit_usd | Float64 | USD value of those deposits: stablecoins at $1, native coin at the block-time or hourly price | | withdrawals | UInt64 | Transfers the casino's hot wallets paid to this wallet in the month, each worth $1 or more | | withdrawal_usd | Float64 | USD value of those withdrawals, priced the same way | | active_days | UInt32 | UTC days in the month with at least one deposit or withdrawal between this wallet and this casino | | first_time | DateTime | Block time of the first deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | last_time | DateTime | Block time of the last deposit or withdrawal in the month, UTC (Parquet timestamp in milliseconds) | | casinos_used | UInt32 | Casinos on this chain that the wallet paid into in the month; 0 when it only received withdrawals | ## 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 3 tables and 36 columns. Only the time range changes. ## Questions buyers ask Q: What is in the Crypto Casino Player Wallets dataset? A: Three Parquet tables, one per chain, with the same 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. It is built from the transfers in our Crypto Casino Deposits and Withdrawals dataset. Q: How big is it? A: We have not run a full month yet, so there is no month total to quote. Test runs give the scale: Stake on Solana had 43,230 wallet rows on 10 November 2026 alone, Rollbit on Tron 4,850 the same day, and Shuffle on Ethereum 4,120 over 10 to 12 November. Exact row counts and file sizes arrive with the delivery manifest. Q: Which casinos and chains are covered? A: 91 brands owned by 89 companies: 73 on Ethereum, 59 on Tron and 75 on Solana, including Stake, Rollbit, Shuffle, Roobet, Rainbet, BC.Game and Gamdom. The list comes from 402 hot wallets in Bitquery's gambling labels, with payment processors such as AlphaPo removed. BSC, Polygon and Base are not in this dataset yet. Q: How do I find the biggest depositors at one casino? A: Filter casino to the brand and deposits above 0, then sort by deposit_usd. Add casinos_used to see whether the wallet also pays rivals, and withdrawal_usd to see how much came back. Sum across months for a longer ranking. Q: Is every wallet a player? A: 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. In a one-day test run on Solana one wallet paid into 40 casinos. Rows with deposits of 0 are wallets that only received money from a casino, which includes moves to exchanges. Q: How is a deposit tied to a casino? A: 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. Tokens are the native coin, USDT and USDC, matched by contract or mint, and transfers under $1 are left out. Q: How were the numbers checked? A: Each table's query ran on a short window before listing. For Shuffle on Ethereum from 10 to 12 November 2026 the dataset has 3,894 withdrawals worth $12,001,881.79. A separate count of the hot wallet's own transfers gave 3,911 worth $12,002,769.68; the 17 extra are moves into Shuffle's own deposit addresses, which we leave out. Tron and Solana were run for one day. No full month has been run yet. Q: What limits should I know about? A: 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 files. casinos_used counts one chain only, and the same person can use different wallets on different chains. A transfer from one casino's hot wallet into another casino's deposit address counts as a deposit by that hot wallet. Q: How do I load it? A: With DuckDB: SELECT wallet, sum(deposit_usd) FROM read_parquet('tron/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. 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 prefix per chain and 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. Each table links to a public sample file. Each has 100 real rows. Tron and Solana are from 10 November 2026 and cover 17 and 20 brands. Ethereum is from 10 to 12 November 2026 and covers Shuffle and Winna only. The samples cover days, not a month, so they find fewer deposit addresses than a full month does. ## 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 transfer data as it happens. Enterprise plan. Topics and schema: https://docs.bitquery.io/docs/streams/kafka-streaming-concepts/#complete-list-of-topics - 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.