RTPLEDGER
On-chain

Casino on-chain transfer activity

Every 24 hours, RTP Ledger reads publicly labeled hot wallets for 9 crypto casinos. The latest run covered 9 casinos. The data describes transfer direction for the listed wallets. The data does not measure payouts, reserves or solvency.

Observed over the last 24 hours
Updated 4 hours ago· 24 Aug 2026
CasinoWallets readInOutValue inValue outDirection
Stake8/85483$3.28M$4.75MInbound-dominant
Duel1/1936586$2.80M$2.75MTwo-way
Rainbet1/11723931$1.48M$3.30MTwo-way
Roobet2/213470$1.55M$2.06MOutbound-dominant
Shuffle1/11639672$1.36M$1.19MTwo-way
Bitcasino3/3124$0$22,144Outbound-dominant
Gamdom2/200$0$0Little observed activity
BC.Game6/600$0$0Little observed activity
Rollbit6/610$0$0Little observed activity

Counts are ERC-20 transfers touching a publicly-labeled hot wallet. Value columns cover USDT and USDC only; transfers of other tokens are counted but not valued. Native ETH and BNB transfers are not observed. An asterisk marks a casino where at least one known wallet could not be read in this run — that is missing data, not zero activity.

A transfer is not a payout. We cannot see whether any given transfer is a player withdrawal, an internal treasury move or an exchange deposit, so this table reports direction only. Snapshot taken 2026-08-24 05:31 UTC.

Scope and limits

Observed data: the report counts transfers in each direction during a fixed window. The report also shows how incoming and outgoing transfer counts change between readings. A large difference between incoming and outgoing transfers can indicate how a labeled wallet is used.

Limits:the chain does not label the purpose of a transfer. An outgoing transfer can be a payout, a treasury move, a hedge or an exchange deposit. The report also excludes unlabeled wallets and cannot show the casino’s total holdings.

Only publicly labeled hot wallets are observable. Casinos without a public label are absent, not inactive.

Method and source policy: methodology · source policy