← All tools

Crash Verifier

Don’t just take the casino’s word for it when your Crash round busts at 1.00x. This tool lets you independently audit any round using the cryptographic seeds provided by the operator.

Crash Verifier

Reproduces the round multiplier from (server seed, client seed, nonce). If the operator's history shows a different multiplier than this tool computes, the round wasn't fair.
Round multiplier
Raw integer h

How to verify your Crash round in 30 seconds

Most modern crypto casinos—like Stake, BC.Game, and Roobet—use a transparent system called “Provably Fair” to generate game outcomes. To audit a past bet, you need to grab three pieces of data from your bet history window:

  1. Server Seed (Revealed): The casino keeps this secret until you change your active seed pair. Once rotated, the old server seed is revealed. You need this revealed hex string.
  2. Client Seed: This is a custom string you or your browser generated. It acts as a client-side modifier.
  3. Nonce: The count of bets made with this active seed pair. The very first bet is 0 or 1, and it increases by one with every bet.
Quick Tip: You can only verify rounds played on an active seed pair that you have already rotated. If you are currently playing on a seed pair, the active server seed is still encrypted (hashed) by the casino to prevent you from predicting future crash points.

The math behind the Crash multiplier

I used to think provably fair was just a clever buzzword to make crypto casinos look clean. Then I actually started running these seeds through my own scripts. Turns out the math is solid. Here is exactly how the game calculates where the rocket crashes:

1. Generating the hash

The game takes the revealed server seed and combines it with your client seed and nonce, separated by a colon. It passes this combined string through an HMAC-SHA256 algorithm:

Hash = HMAC-SHA256(Server_Seed, "Client_Seed:Nonce")

2. The instant bust check (Modulo trick)

The house edge on most crash games is 3%. Not awful, but it adds up over a long session. Contrast that with blackjack at 0.5%—very different playstyles.

To secure this 3% edge, the game takes the first 13 hexadecimal characters (52 bits) of the generated hash, converts them to a decimal integer (we’ll call it h), and checks if it is divisible by 33:

If (h mod 33 == 0) -> Game busts instantly at 1.00x

The game busted at 1.00x five times in an hour. Absolute robbery. But now you can check if those 1.00x instant busts were mathematically pre-determined or if the operator is cheating. If h mod 33 == 0, the round was indeed a fair, pre-determined instant bust.

3. Scaling the multiplier

If the round passes the instant-bust check, the decimal integer h is scaled using a specific limit formula:

Multiplier = floor((100 * e - h) / (e - h)) / 100

Where e = 2^52 (the maximum value of a 52-bit integer, or 4,503,599,627,370,496). This mathematical model guarantees that while high multipliers (like 1,000x or 10,000x) are possible, the probability scales down strictly according to the formula.

Strategy: How to use this tool to stay safe

Before implementing an advanced betting strategy (such as the systems in our Crash game strategy guide), you must establish absolute confidence in the game’s integrity. We recommend combining this verifier with our Crash Cashout Explorer to model optimal payout targets.

  • Perform random audits: Don’t verify every single bet. Instead, rotate your seed pair at the end of a session, copy the last 5-10 nonces, and paste them here (or in our Universal Verifier) to see if the multipliers match perfectly.
  • Verify during streaks: If you hit a suspicious streak of low crash points (e.g., ten rounds in a row crashing under 1.2x), run the seeds. If even a single decimal digit differs, the casino has compromised the fairness of the game.

Frequently asked questions

Can the casino change the crash point after I place my bet?

No. Because the server seed hash is published before you place your bets, the outcome is locked in. If the casino changed the server seed to force a bust, the revealed seed at the end of your session would fail to match the hash shown at the start, instantly exposing the fraud.

Why did my round verify with a different multiplier than what I saw on screen?

Double-check your house edge setting. While 3% (mod 33) is the Stake default, some newer casinos use a 1% house edge (mod 101) or a 2% house edge (mod 50). Using the wrong modulo setting will result in a different multiplier than the one calculated by the casino.

Is there a cheat or predictor for the Crash game?

No. Since the outcome is determined using a secure cryptographic hash (HMAC-SHA256) of a server seed that remains encrypted until rotated, there is no way to predict the crash point in advance. Any software claiming to predict crash points is a scam designed to steal your casino balance or personal data.