Loading
Loading
Every draw can be checked by anyone. Completed draws will be listed here.
The transaction in which the winning ticket was picked. It's linked from each result on our Winners page.
Your browser checks the public record directly, not our servers. The public service it uses can see your IP address.
The tickets were locked in
An independent service picked the number
The maths picks the winner
Your browser reads the draw from the Polygon blockchain through a public node — not from our servers or our database — and recalculates the winning ticket, step by step.
Two independent public node operators. Run the check through each to compare their answers. If the one you choose can't answer, your browser tries the other and the page says so.
Checking sends read-only requests from your browser to the node operator you choose — or, if that one can't answer, the other — who can see your IP address. The check makes no requests to our servers.
The result transaction holds two records. The draw contract's WinnerSelected log gives the winning ticket. Chainlink's RandomWordsFulfilled log, which follows it, gives the request it answered and Chainlink's random output. The random number the contract received is calculated from that output the same way Chainlink's coordinator calculates it: keccak256(output, 0).
The contract draws from the tickets actually in the draw, not the full ticket cap. That number is announced on-chain at least 24 hours before randomness can be requested. This step finds both records and checks they agree.
Chainlink VRF answers through a coordinator contract, which checks a cryptographic proof on-chain before it releases a number. The draw contract's coordinator can be changed — by its owner, or by Chainlink's coordinator when Chainlink moves to a new version — so this step checks that both the request and the answer for this draw went through Chainlink's published coordinator for Polygon.
The contract divides the random number by the number of tickets and keeps the remainder, then adds 1 — so the result is always one of the tickets in the draw. Your browser runs the same formula.
Entrants don't see their tickets in the order they were entered — each Jackpot maps entry order to a different ticket number, so a ticket number doesn't reveal how many were entered or when. Your browser applies the same mapping, with the same code, that the rest of this site uses.