Transaction eec4634d5eda9a80ade6677eb35a9b29c3eaac8444c323e614c6a593137bf6bd

eec4634d5eda9a80ade6677eb35a9b29c3eaac8444c323e614c6a593137bf6bd:1

  • Processed time: 2012-06-24 08:25:52
  • Key date: 2012-06-24
  • Bet: lessthan 32000
  • Bet TX: eec4634d5eda9a80ade6677eb35a9b29c3eaac8444c323e614c6a593137bf6bd
  • Payment TX: ec815f664302c1f119c557847b7f1a10cb9c83243aee52903cc2463584a779d6
  • Payment TX Status: CONFIRMED
  • Bet Amount: 0.01000000
  • Outcome: LOSE
  • Payment: 0.00000001
  • Address: 1GiiXPh45cPJwECVWvsx3ND2PTCaQMhXCq
  • Lucky number: 51722

    • 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-24 in hash.keys
    sha256(UvlLtRLuoglhog08VT78TS96dvQh2RIdV5LJ0BkQEDfEc8Ot5xqynkcpw2m1C3Y6) -> 5042e5ed311d28d4766a26de0657c96bc08ef9ef10a40ba041e54a58d99d7155

    Secret and Transaction Hash

    Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
    hmac_sha512(UvlLtRLuoglhog08VT78TS96dvQh2RIdV5LJ0BkQEDfEc8Ot5xqynkcpw2m1C3Y6,eec4634d5eda9a80ade6677eb35a9b29c3eaac8444c323e614c6a593137bf6bd) -> ca0a64bfa2904d816c89ff8a8117ffca24f9c8d2bb7de030923d08b378de2cfb hmac512

    Lucky Number

    Verify that the first bytes of the bet hash above is the lucky number
    ca0a64bfa2904d816c89ff8a8117ffca24f9c8d2bb7de030923d08b378de2cfb -> ca0a -> 51722