BitqueryBitqueryData Store
Multi-chain logoMulti-chainTransfersLabels

Crypto Casino Deposits and Withdrawals

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

Coverage
Last 12 monthsto Oct 15, 2026 · yesterday
Tables
6Parquet, one prefix each
Columns
84across 6 tables
Coverage ends yesterday, UTC

Overview

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

Use cases

  • 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

6 tables

84 columns · free sample for each table

ethereum_casino_transfers

14 columns

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

ethereum/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

tron_casino_transfers

14 columns

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

tron/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

bsc_casino_transfers

14 columns

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

bsc/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

polygon_casino_transfers

14 columns

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

polygon/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

base_casino_transfers

14 columns

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

base/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

solana_casino_transfers

14 columns

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

solana/casino_transfers<YYYY-MM>.parquetone file per calendar month (ZSTD)
Browse columns Sample fileSample updated Oct 16, 2026

Schema reference

copies a column name
84 columns
ethereum_casino_transfers14 columnsCasino deposits and withdrawals on Ethereum, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file
tron_casino_transfers14 columnsCasino deposits and withdrawals on Tron, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file
bsc_casino_transfers14 columnsCasino deposits and withdrawals on BSC, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file
polygon_casino_transfers14 columnsCasino deposits and withdrawals on Polygon, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file
base_casino_transfers14 columnsCasino deposits and withdrawals on Base, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file
solana_casino_transfers14 columnsCasino deposits and withdrawals on Solana, one row per transfer.
ColumnTypeDescription
chainStringethereum, tron, bsc, polygon, base or solana
block_numberUInt64Block number (slot on Solana)
block_timeDateTimeBlock time, UTC
tx_hashStringTransaction hash (signature on Solana; no 0x on Tron)
casinoStringCasino brand from Bitquery labels, e.g. stake, rollbit, bcgame
directionStringdeposit or withdrawal
wallet_roleStringdeposit_address (money into a per-player deposit address) or hot_wallet
from_addressStringSender (owner wallet on Solana)
to_addressStringReceiver (owner wallet on Solana)
token_symbolStringNative coin, USDT, USDC or USDC.e
token_addressStringToken contract or mint; empty for the native coin
amountDecimalAmount moved, decimal adjusted, as a decimal string
amount_usdFloat64USD value: stablecoins at $1, native coin at the block-time or hourly price
price_sourceStringWhere amount_usd came from
Sample file

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.

Start with

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 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:

# ethereum_casino_transfers: one file per calendar month (ZSTD)
ethereum/casino_transfers<YYYY-MM>.parquet

# tron_casino_transfers: one file per calendar month (ZSTD)
tron/casino_transfers<YYYY-MM>.parquet

# bsc_casino_transfers: one file per calendar month (ZSTD)
bsc/casino_transfers<YYYY-MM>.parquet

# polygon_casino_transfers: one file per calendar month (ZSTD)
polygon/casino_transfers<YYYY-MM>.parquet

# base_casino_transfers: one file per calendar month (ZSTD)
base/casino_transfers<YYYY-MM>.parquet

# solana_casino_transfers: one file per calendar month (ZSTD)
solana/casino_transfers<YYYY-MM>.parquet
  1. Download a free sampleNo email needed.
  2. Pay nowName, work email and licence check.
  3. Pay the invoiceBy card or bank transfer.
  4. Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.

Time windows

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

30 days
Latest month
Sep 15, 2026 → Oct 15, 2026
$300
Pay now
365 days
Last 12 months
Oct 15, 2025 → Oct 15, 2026
$3,000
Pay now
In every window
  • All 6 tables, 84 columns
  • Parquet files in the layout under Delivery
  • S3 or R2 download, chosen at checkout
  • Licensed under the Data License

FAQ

8 questions
What is in the Crypto Casino Deposits and Withdrawals dataset?

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.

Which brands are covered?

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.

How is a deposit address found?

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.

Can one transfer appear twice?

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.

How were the tables checked?

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.

How do I load it?

With DuckDB: SELECT casino, direction, sum(amount_usd) FROM read_parquet('ethereum/*.parquet') GROUP BY 1, 2 ORDER BY 3 DESC. pandas, Polars, Spark and ClickHouse read the same files.

How is the data delivered?

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.

Can I try before I buy?

Yes. Each table links to a public sample file with real rows from September and October 2026. No email address required.