Recompute the Plinko path and landing bucket from your revealed seeds. Set the row count to exactly what the round used.
Computed locally via the Web Crypto API (HMAC-SHA256). Your seeds and nonce are never sent anywhere — the only network request on this page is an anonymous, cookieless page-view counter (page path + referring page, nothing you type). It's the same code we test against Stake's own calculator.
In Plinko a ball drops through rows of pegs, bouncing Left or Right at each one; the bucket it lands in is simply the number of Rights. One float decides each row, so an 8-row drop uses 8 floats, a 16-row drop uses 16.
The result comes from the standard Stake-style byte stream:
HMAC-SHA256( key = server_seed , message = "client_seed:nonce:round" )For each of the rows floats: f < 0.5 → Left, otherwise Right. The bucket index is the count of Rights (0 … rows):
path = [L/R for each row]
bucket = number of R's → 0 … rowsStake's calculator shows the directions (0 = left, 1 = right); the bucket is their sum, counted from the far-left bucket 0.
Each row consumes one float: below 0.5 is Left, at or above 0.5 is Right. The landing bucket equals the total number of Rights.
Almost always the row count. You must set exactly the same number of rows the round used — a different row count gives a different (but still correct) result.
Yes. More rows means more floats consumed and a different path, so always match the round's row setting.
Stake / Stake.us — we checked the left/right directions against Stake.us' own calculator. Other casinos match only if they use exactly Stake's Plinko algorithm; not tested by us.
Formula checked bit-for-bit against Stake.us' own calculator (Aug 2026). Other casinos not tested. Other games: Dice · Limbo · Plinko · Mines · Keno · all verifiers. Open methodology: /methodology/. © FairPlay Audit — independent, free and open source (MIT).