Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Prescott Valley, Arizona

Edward Kayer, 42, from Prescott Valley, Arizona, on 22 March 2021

Victim Info

  • Edward Kayer
  • White/European American
  • 42
  • Male


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
  • 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


Source ID: 29869 - Fatal Encounters

Cross References

This report has possible entries from multiple sources


Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58852. Submitted in Mainchain Tx AE74F5509E2D3E672BB9AFBDF8F6277D797C6C25049414860CC61CB27DA35A33, at block height 4908733

Transaction details

Tx AE74F5509E2D3E672BB9AFBDF8F6277D797C6C25049414860CC61CB27DA35A33
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: Vuoi9C2khEWM1pRgfQL+GjkhifGgR22Ytj0qoMKZd0tb53a3jtMEOfshwxbaS1KN+OFBF6qFZytFshJSqot/YQ==
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: