Transaction df3cf493ab78137f917dd56e8c8e3a09d9bf2371a451e5dc05c11abf367ebacc

df3cf493ab78137f917dd56e8c8e3a09d9bf2371a451e5dc05c11abf367ebacc:1

  • Processed time: 2012-06-09 06:15:12
  • Key date: 2012-06-08
  • Bet: lessthan 512
  • Bet TX: df3cf493ab78137f917dd56e8c8e3a09d9bf2371a451e5dc05c11abf367ebacc
  • Payment TX: d36fcaea94cf65d212028036740b77f4be0468077228b289e42ff5131af0f924
  • Payment TX Status: CONFIRMED
  • Bet Amount: 1.00000000
  • Outcome: WIN
  • Payment: 125.44450000
  • Address: 174ezTGN3ZAkzbcHTizsaT4ymDeY6GCxRb
  • Lucky number: 26

    • Validation

    Secret hashes

    Download and verify hash.keys

    For more details on the secret keys see secrets

    Using correct secret key

    Verify that the secret used hashes to the hash listed for for 2012-06-08 in hash.keys
    sha256(w6ysVVDzZig9UOnfJTpJ9GWXTbUvLrVkmOye48esls5B5wl2RvuZ8TPtvRY0FR2C) -> fadd0c21d72f1520e73686f9b534ce74b014767fc12e5fe351510b8fd7fe8100

    Secret and Transaction Hash

    Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
    hmac_sha512(w6ysVVDzZig9UOnfJTpJ9GWXTbUvLrVkmOye48esls5B5wl2RvuZ8TPtvRY0FR2C,df3cf493ab78137f917dd56e8c8e3a09d9bf2371a451e5dc05c11abf367ebacc) -> 001a1a2e19ef1169a7099e237c0901030d3aaa2150cf466514667c81f329687d hmac512

    Lucky Number

    Verify that the first bytes of the bet hash above is the lucky number
    001a1a2e19ef1169a7099e237c0901030d3aaa2150cf466514667c81f329687d -> 001a -> 26