Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62
Download and verify hash.keys
For more details on the secret keys see secrets
Verify that the secret used hashes to the hash listed for for 2012-06-17 in hash.keys
sha256(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz) -> f2bdcab058c3c9c6f460a0b4b3c049503f2dfe57f91ef44f8779544e56027588
Verify that the hmac sha512 with secret and transaction_id hash to the bet hash
hmac_sha512(nJawTR7RIrciXb3JIYp9Qoh7YJ1QALxlnQJw3veDN4UkecWcMNa2woxV6y891GXz,38f381893d3cdcc8f7ea3e11d098f8e7b4daa60e904a62ef0ab4798fa996def8) -> 003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 hmac512
Verify that the first bytes of the bet hash above is the lucky number
003edf82a3b5a6680a6ede36a573cbf59f7f8d9f1200884755573c66d6d68190 -> 003e -> 62