Crash live tracker

Live Duel Crash tracker — every round captured

Every Duel Crash bust recorded with the same depth as the Stake and Roobet trackers — multiplier history, instabust frequency, ≥10× rate, hourly distribution, longest streaks, rolling RTP. Plus drand-beacon verification baked into every detail page.

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 Duel Crash is verifiable

Unlike most casinos, Duel pins each round's randomness to a [drand random-beacon](https://drand.love/) entry committed before the round starts. That means you don't have to trust Duel's seed rotation — the randomness is timestamped on a public, distributed beacon that nobody (including Duel) can rewrite after the fact.

Each row in the tracker carries the round's drand_randomness and server_seed — copy them into our [Duel Crash verifier](/verify/duel-crash) for an independent recomputation of the bust point.

Duel Crash RTP

99.9% on the standard mode (0.1% house edge). The math is crashPoint = max(1.0, 2^32 / (value + 1) × 0.999) where value is the first 4 bytes of HMAC-SHA256(serverSeed, drandRandomness:0) interpreted as a uint32.

Duel Crash vs Stake / Roobet Crash

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

• Stake uses a per-bet (serverSeed, clientSeed, nonce) triple with a 52-bit slice + 1-in-33 instant-bust rule.
• Roobet uses a per-round (serverSeed, publicKey) pair with the same 52-bit slice formula.
• Duel uses (serverSeed, drandRandomness) with a 32-bit slice and a 0.1% edge baked into the formula directly (no instant-bust path).

The result is similar variance across all three but the entropy sources are completely independent — a 100× on Duel doesn't influence Stake or Roobet (and vice versa).

Telegram alerts for Duel 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 Duel Crash? 99.9% (0.1% house edge baked into the formula).

Is Duel Crash provably fair? Yes — and stronger than per-seed verification: each round commits to a drand beacon entry, so the randomness is anchored to a public timestamped feed that even the casino can't predict.

Can you predict Duel Crash bust points? No. The drand beacon is provably unpredictable until publish; the server seed is committed pre-round and only revealed afterward.

Are Duel Crash and Stake Crash the same game? Same design, different math and different randomness source. Independent histories.

How do I verify a round myself? Open any round in the history → paste the server_seed + drand_randomness into the [verifier](/verify/duel-crash) → see the exact bust point recomputed in your browser.