# Crypto Casino Deposits and Withdrawals | Bitquery Data Store

Every deposit into and withdrawal out of 93 crypto casino brands on six chains, one row per transfer, USD-priced.

Dataset page: https://bitquery.io/datastore/datasets/crypto-casino-transfers
Network: Multi-chain
Category: Transfers, Labels
Tables: 6
Columns: 84
Coverage: first block to 2026-10-16
Format: Apache Parquet, ZSTD compression, one prefix per table
Licence: https://bitquery.io/datastore/legal/data-license

## What this is

Crypto casinos take deposits in two ways. Most give each player a deposit address that forwards the money to the site's hot wallet, and some players pay the hot wallet directly. Payouts leave from the hot wallets, and so does every other transfer out, such as a move to an exchange. This dataset keeps one row for each of those transfers, for 93 casino brands owned by 90 companies, from Bitquery's own gambling hot-wallet labels: 613 addresses on Ethereum, Tron, BSC, Solana, Polygon and Base.

Each row names the brand, the direction (deposit or withdrawal) and the wallet role (deposit address or hot wallet), with the block, transaction, sender, receiver, token, amount and USD value. Tokens are the native coin plus USDT and USDC, matched by contract or mint, so fake tokens with copied names never appear. Moves between a casino's own wallets are left out, and so are transfers under $1.

## What people use it for

- Deposit and withdrawal volume per brand, per chain and per token
- Market share by brand, measured from money that actually moves
- Players who pay into more than one brand, from shared payer wallets
- Compliance screening: which wallets send money to or get paid by gambling sites

## Tables (6)

### ethereum_casino_transfers: 14 columns

Casino deposits and withdrawals on Ethereum, one row per transfer.

Bucket prefix: ethereum/casino_transfers
File naming: <YYYY-MM>.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_transfers/sample_2026-09-30.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

### tron_casino_transfers: 14 columns

Casino deposits and withdrawals on Tron, one row per transfer.

Bucket prefix: tron/casino_transfers
File naming: <YYYY-MM>.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_transfers/sample_2026-09-30.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

### bsc_casino_transfers: 14 columns

Casino deposits and withdrawals on BSC, one row per transfer.

Bucket prefix: bsc/casino_transfers
File naming: <YYYY-MM>.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/casino_transfers/sample_2026-10-14.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

### polygon_casino_transfers: 14 columns

Casino deposits and withdrawals on Polygon, one row per transfer.

Bucket prefix: polygon/casino_transfers
File naming: <YYYY-MM>.parquet, one file per calendar month (ZSTD)
Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/polygon/casino_transfers/sample_2026-09-30.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

### base_casino_transfers: 14 columns

Casino deposits and withdrawals on Base, one row per transfer.

Bucket prefix: base/casino_transfers
File naming: <YYYY-MM>.parquet, one file per calendar month (ZSTD)
Free sample (real Parquet, no email needed): https://bitquery-blockchain-dataset.s3.us-east-1.amazonaws.com/base/casino_transfers/sample_2026-09-30.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

### solana_casino_transfers: 14 columns

Casino deposits and withdrawals on Solana, one row per transfer.

Bucket prefix: solana/casino_transfers
File naming: <YYYY-MM>.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_transfers/sample_2026-09-30.parquet
Sample updated: Oct 16, 2026

| column | type | description |
| --- | --- | --- |
| chain | String | ethereum, tron, bsc, polygon, base or solana |
| block_number | UInt64 | Block number (slot on Solana) |
| block_time | DateTime | Block time, UTC |
| tx_hash | String | Transaction hash (signature on Solana; no 0x on Tron) |
| casino | String | Casino brand from Bitquery labels, e.g. stake, rollbit, bcgame |
| direction | String | deposit or withdrawal |
| wallet_role | String | deposit_address (money into a per-player deposit address) or hot_wallet |
| from_address | String | Sender (owner wallet on Solana) |
| to_address | String | Receiver (owner wallet on Solana) |
| token_symbol | String | Native coin, USDT, USDC or USDC.e |
| token_address | String | Token contract or mint; empty for the native coin |
| amount | String | Amount moved, decimal adjusted, as a decimal string (cast to DECIMAL to sum) |
| amount_usd | Float64 | USD value: stablecoins at $1, native coin at the block-time or hourly price |
| price_source | String | Where amount_usd came from |

## Price

- Latest month (Sep 16, 2026 → Oct 16, 2026): $300 one-time, USD
- Last 12 months (Oct 16, 2025 → Oct 16, 2026): $3,000 one-time, USD

Every window includes all 6 tables and 84 columns. Only the time range changes.

## Questions buyers ask

Q: What is in the Crypto Casino Deposits and Withdrawals dataset?
A: Six Parquet tables, one per chain, with the same 14 columns: chain, block, time, transaction, casino, direction, wallet role, sender, receiver, token symbol, token address, amount, USD value and price source.

Q: Which brands are covered?
A: 93 brands owned by 90 companies, including Stake, Rollbit, Shuffle, Roobet, Rainbet, BC.Game, Gamdom and Duel. The list comes from Bitquery's gambling labels, with payment processors such as AlphaPo removed. The wallet list is a snapshot of those labels and grows as they are updated.

Q: How is a deposit address found?
A: A wallet counts as a deposit address in a month when it forwards 80 to 125 percent of what it receives to one brand's hot wallets and has at most 50 senders. Every transfer into it that month is then a deposit to that brand.

Q: Can one transfer appear twice?
A: Yes, in one case. When one site's hot wallet pays a player straight into another site's deposit address, the row is a withdrawal for the first and a deposit for the second.

Q: How were the tables checked?
A: For Ethereum in September 2026, withdrawals per brand came within 1 percent of our multi-casino players study, and a second, separate query matched both deposits and withdrawals to the cent. The other chains were run on one day and on sample casinos.

Q: How do I load it?
A: With DuckDB: SELECT casino, direction, sum(amount_usd) FROM read_parquet('ethereum/casino_transfers/*.parquet') GROUP BY 1, 2 ORDER BY 3 DESC. pandas, Polars, Spark and ClickHouse read the same files.

Q: How is the data delivered?
A: 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 where to collect them: a Requester Pays S3 bucket, downloaded with your own AWS account, or a Cloudflare R2 bucket with a read-only API key and no egress fees. 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 of up to 1,000 real rows from one day: 30 September 2026, or 14 October 2026 for BSC. A sample covers 2 to 52 brands. It takes rows of each type in near-equal numbers where the day has enough of them, so its mix of row types does not match the full data. The BSC and Solana samples come from a one-day run and leave out direct payments to hot wallets, because one day of data cannot tell those apart from deposit addresses passing money on. No email address required.

## 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.