, from Sacramento, California - shot on 27 August 2022
Details
Additional Evidence
- 2022-08-27
- shot
- knife
- F
- Sacramento
- CA
- False
- attack
- Not fleeing
- False
- True
Source
Source ID: 8379 - Washington Post
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 125187. Submitted in Mainchain Tx 94875387EAA442B22223D712D1C44ACA411262571FF5C084EE6116491289AA9A, at block height 1287612
Transaction details
Tx 94875387EAA442B22223D712D1C44ACA411262571FF5C084EE6116491289AA9A
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: vWld5kmnehav9vkcf+QsJiAvwAUNr4osoEXHKbTa4G8Ho9Tit85LGRezSzGft1+Pmm62MaH74swuz7BXm0AgGQ==
Raw Tx data:
Hash Comparison
Hash stored in database: c4535487731abd685c9f4885c8e9a488522b7d7a755bd1a892af023c121c8ab0
Hash from Mainchain Tx: 1662078666
Dynamically generated hash: c4535487731abd685c9f4885c8e9a488522b7d7a755bd1a892af023c121c8ab0
Hashes Match?How is the comparison calculated?
The hash stored in the database is used as the identifier for this report, and can be seen in the URL. The hash from the Mainchain Tx is the hash sent to and stored on Mainchain. Finally, the "generated hash" is generated each time this page is loaded, using the same data used for the hash submitted to Mainchain.
Raw data used to generate the hash, using the Node.js crypto.createHash('sha256') algorithm: