Recompute the Mines layout from your revealed seeds. Set the mine 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.
Mines hides N bombs among 25 tiles. The layout isn't picked all at once — it's drawn sequentially without replacement, one float per mine, exactly the way Stake shows it on its calculation page.
The result comes from the standard Stake-style byte stream:
HMAC-SHA256( key = server_seed , message = "client_seed:nonce:round" )Start with tiles 0–24. For each mine, take one float and remove that tile from the remaining pool:
for each mine:
idx = floor( f × tiles_remaining )
mine = pool[idx]; remove it from poolThe result is the list of mine tiles in draw order — the first N numbers of Stake's "Number to Shuffle" list. Tile numbers 0–24 are the ones Stake's calculator shows.
Tiles 0–24 are drawn one at a time without replacement: idx = floor(float × tiles remaining). The first N draws are the mine positions, in the order they were drawn.
Stake's calculator lists the tiles in the sequence they were drawn. The mines are the first N tiles of that list, so the order tells you which tiles are mines for a given mine count.
Yes — more mines consume more floats. Always set the same mine count the round used.
No. Nothing is computable until the server seed is revealed; this tool only checks a finished round.
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).