Shuffle Plinko Verifier

Recompute the ball path and landing bucket for one bet on Shuffle from the server seed, client seed and nonce. Same HMAC-SHA256 stream the operator publishes, run in your browser.

Verify one betAnalyze a range

Casino

Game

Have a bet link? paste it; we open the right casino and game and tell you where the seeds are. Nothing is sent anywhere.

Examples

Verification Inputs

Server Seed unhashed, revealed after you rotate

Client Seed your chosen seed

Nonce bet counter, starts at 0

Server Seed Hash optional, the SHA-256 shown before you bet

Rows 8 to 16

Recomputes as you type. Nothing leaves your browser.

Plinko Result

Paste the server seed and client seed from the bet. The plinko result appears here as you type.

Algorithm sourceShuffle Help Center, Provably Fair: Implementation + Game Eventschecked 2026-09-20

Shuffle documents the same byteGenerator (HMAC-SHA256 over clientSeed, nonce and cursor; 32 bytes as 8 four-byte floats) and the same event mapping for the games listed here (article revision 2026-08-12). Its code blocks are images, so the prose is what was checked. Not listed: Crash and Slide (hash-chain seeded), Limbo and Tower (formula and difficulty table not in the prose), Coinflip and Hilo (side and card index order not in the prose).

Shuffle fairness page Shuffle on GAMB·8

How Shuffle derives a Plinko result

From float to result

One float per row. A float below 0.5 sends the ball left, 0.5 or above sends it right. The bucket is the number of rights, so with 16 rows there are 17 buckets and the middle ones are far more likely.

What to compare

Count the bucket from the left edge, starting at 1, and compare with the multiplier slot in your bet history.

Where the seeds are

Open the bet in your history on Shuffle. The client seed and nonce show immediately. The unhashed server seed appears only after you rotate your seed pair, so rotate first, then verify every bet from the old pair.

The byte stream, Shuffle

bytes = HMAC_SHA256(key = serverSeed, msg = clientSeed:nonce:round) // round starts at 0float = b0/256 + b1/256^2 + b2/256^3 + b3/256^4 // 4 bytes per floatresult = game event mapping applied to the floats, in order

Other Shuffle games

Shuffle Dice verifier Shuffle Mines verifier Shuffle Keno verifier Shuffle Roulette verifier Shuffle Wheel verifier Stake Plinko verifier Stake.us Plinko verifier Winna Plinko verifier

Keep what you worked out.

A free account saves your bankroll plans, sessions and the results you run here, on every device. No card, no upsell.

Create free account All tools

Frequently Asked Questions

Why does the ball rarely reach the edge buckets?

Reaching the leftmost bucket needs every row to go left, a 1 in 65,536 event at 16 rows. The distribution is binomial, which is why the centre pays least.

Does the risk level change the path?

No. Risk only changes the payout table under the buckets. The path is the same for the same seeds and nonce.

Which Shuffle algorithm does this use?

Shuffle Help Center, Provably Fair: Implementation + Game Events, read 2026-09-20. The byte stream is HMAC-SHA256 of clientSeed:nonce:round keyed by the server seed, converted to 4-byte floats, then mapped to the ball path and landing bucket.

Do my seeds leave the browser?

No. The HMAC and SHA-256 run with the Web Crypto API on your device. The share link carries the seeds only because you copied it.