trackersino
stale
18+Data only · No predictions · Play responsiblyHow this site works
BetaInvestigatingPublic beta · expect occasional gaps while we stabilise feeds.
Shuffle · crash original

Crash live tracker

Live crash points from Shuffle.com's public GraphQL endpoint. Seed chain anchored to a Bitcoin block hash. ~1 round every 15-20s.

Window
Last crashINSTABUST
Shuffle · crash original

Crash live tracker

connecting…

Rounds (24h)
0
finalized
Mean crash
median —×
Max crash
p95 —×
Insta-bust < 1.5×
0 / 0
≥ 10× rate
fair-game baseline ≈ 9.80%

Recent crash points · last 120

newest first
Loading…
Loading…

Spin history

0 matching · last 2000 loaded
RoundMultiplierFinalizedRandom
No rounds in this filter.
rows
page 1 / 1

Biggest wins · 24h

payout = bet × target
Loading…

Live Shuffle Crash tracker — every round captured

Shuffle.com runs one of the cleanest Crash variants in the crypto-casino space. Every settled round is captured here with the same depth as the Stake / Roobet / Duel trackers — multiplier history, instabust frequency, ≥10× rate, hourly distribution, longest streaks, rolling RTP.

What this page tracks

  • Live ribbon of recent bust points.
  • Round history sortable on every column, filterable by time window.
  • Multiplier distribution histogram.
  • Instabust % under 1.5× and ≥10× rate.
  • Hourly buckets showing time-of-day variability.
  • Biggest crashes ranked.
  • Streak tracker per threshold.
  • Rolling RTP estimate from observed bust points.

How Shuffle Crash verification works

Shuffle's seed chain is anchored to a future Bitcoin block hash chosen pre-launch — once that block was mined, the entire chain of round seeds became cryptographically unfalsifiable. Each round's revealed server seed is the SHA-256 hash of the previous round's seed, so the chain can be walked backwards from any known round to verify every prior one.

The math: crashPoint = floor(99 × 2^32 / value) / 100 where value is derived from HMAC-SHA256(serverSeed, "<BTC-block-hash>") reduced to a uint32 (with rejection of values producing < 1.00×). 99% RTP.

Shuffle Crash vs Stake / Roobet / Duel Crash

Same player-facing design (multiplier-cashout). Different math and entropy sources:

  • Stake / Roobet: per-bet (serverSeed, clientSeed, nonce) triple, 52-bit slice, 1-in-33 instant bust.
  • Duel: per-round (serverSeed, drandRandomness) pair, 32-bit slice, 0.1% edge baked into the formula.
  • Shuffle: SHA-256 seed chain anchored to a Bitcoin block, 32-bit slice, 1% edge baked into the formula.

Independent seed chains, independent histories — a 100× on Shuffle has zero correlation with the other three.

Telegram alerts for Shuffle Crash

Common alert configurations: 100×+ crashes, ≥10× drought across 50 rounds, rolling RTP > 130% across the recent window, heaviest crash of the day. [Set up alerts](/settings).

FAQ

What's the RTP of Shuffle Crash? 99% (1% house edge baked into the formula).

Is Shuffle Crash provably fair? Yes — and the seed chain is anchored to a Bitcoin block hash chosen before the chain launched, so the casino cannot rewrite history even in principle.

Can you predict Shuffle Crash bust points? No. Once a round's server seed is revealed it can be verified, but until then the chain is one-way.

How is Shuffle Crash different from Stake / Roobet? Different math (32-bit slice + baked-in edge, no instant-bust path) and different randomness source (BTC-block-anchored seed chain vs per-bet HMAC).