Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Prescott Valley, Arizona

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.

Additional Evidence

  • Edward Kayer
  • 42
  • Male
  • White
  • Antelope Meadows Road and Dogtown Road
  • Prescott Valley
  • AZ
  • 86315
  • Yavapai
  • Yavapai County Sheriff's Office
  • AZ0130000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • attack
  • foot
  • Suburban
  • https://fatalencounters.org/wp-content/uploads/2021/04/Edward-Kayer.jpg
  • Violent Crime
  • shooting

Source

Source ID: 8760 - Mapping Police Violence

Cross References

This report has possible entries from multiple sources

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65244. Submitted in Mainchain Tx 11C5B52D354684D13FF39449AFD3CBE33628DF3F91719F335769FF6B54C6F2D5, at block height 140343

Transaction details

Tx 11C5B52D354684D13FF39449AFD3CBE33628DF3F91719F335769FF6B54C6F2D5
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: mEN0fbFKfSTYXro2fngBsH0tZSiXm/WrtHkMk7S4e8t/8iJAWKymcuf9zPkCHDYv+spFJZm7iX/dUvyFTXlpYA==
Raw Tx data:

Hash Comparison

Hash stored in database: 3db133a097158fd85f892d737324ea1591e3e9e184d4c6267b3be7587a836ce4

Hash from Mainchain Tx: 3db133a097158fd85f892d737324ea1591e3e9e184d4c6267b3be7587a836ce4

Dynamically generated hash: 3db133a097158fd85f892d737324ea1591e3e9e184d4c6267b3be7587a836ce4

Hashes Match?
YES

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: