Edward Kayer, 42, from Prescott Valley, Arizona, on 22 March 2021
Victim Info
- Edward Kayer
- White/European American
- 42
- Male
Details
Edward Kayer was wanted in connection to an incident at a restaurant where he was suspected of firing more than a dozen rounds then taking off. Sedona police called for help from Prescott police after they tried to pull Kayer over as he rode a motorcycle, but he fled. Kayer abandoned his ride then took off on foot. At around 10 p.m., police found Kayer hiding in a field where he allegedly fired at deputies who shot and killed him.Primary Evidence & Links
Additional Evidence
- Edward Kayer
- 42
- Male
- European-American/White
- European-American/White
- Not imputed
- Antelope Meadows Road and Dogtown Road
- Prescott Valley
- AZ
- 86315
- Yavapai
- Antelope Meadows Road and Dogtown Road Prescott Valley AZ 86315 Yavapai
- Yavapai County Sheriff's Office
- Pending investigation
- https://fatalencounters.org/wp-content/uploads/2021/04/Edward-Kayer.jpg
Source
Source ID: 29869 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Mapping Police Violence -Edward Kayer, 42, from Prescott Valley, Arizona, on 22 March 2021
- Washington Post -Edward Kayer, 42, from Tucson, Arizona - shot on 22 March 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65247. Submitted in Mainchain Tx F01868DE309D2458EAE0AE0C31A7AE56D6329D32D8B2A95E0847799F7F535B58, at block height 140346
Transaction details
Tx F01868DE309D2458EAE0AE0C31A7AE56D6329D32D8B2A95E0847799F7F535B58
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: RZO/qo2ablLGXZQp2Fbz8BWmnbgc2tAf2jsM1L8cqoY5w4gUs7z3mHaQ6FllTnFPTIpJBuCR+62qhaHSi1KC9Q==
Raw Tx data:
Hash Comparison
Hash stored in database: 321325e27699ea13176dbea004dac229bf8a97e79f6639e8e79f9be64e3d13dc
Hash from Mainchain Tx: 321325e27699ea13176dbea004dac229bf8a97e79f6639e8e79f9be64e3d13dc
Dynamically generated hash: 18259a99db6393072f0cb793ce762454a1dfe50a7e0c0f2584f7c2dc3470a788
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: