Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Maysville, Kentucky

Name withheld by police, from Maysville, Kentucky, on 29 March 2021

Victim Info

  • Name withheld by police
  • Unknown
  • Male

Details

At 4:30 p.m., a Fleming County deputy attempted to stop a vehicle in which a man and a woman appeared to be involved in a physical altercation, police said. The male driver exited the vehicle and the deputy chased him. Upon catching him, the deputy and the man reportedly struggled, and the deputy shot and killed the man.

Additional Evidence

  • Name withheld by police
  • Male
  • KY-11
  • Maysville
  • KY
  • 41056
  • Mason
  • Fleming County Sheriff's Office
  • KY0350000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Unarmed/Did Not Have Actual Weapon
  • no object
  • attack
  • not fleeing
  • Rural
  • Traffic stop/Disturbance
  • physical altercation in vehicle

Source

Source ID: 8737 - 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 65144. Submitted in Mainchain Tx 85C76D62FDD240DC68641407831EE6D73C150605BBCCBBFBE6B1C8BAF64691A2, at block height 139478

Transaction details

Tx 85C76D62FDD240DC68641407831EE6D73C150605BBCCBBFBE6B1C8BAF64691A2
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: wNPYPW3zlkV7rbYx2D+szk3pKRIIHv1dmR6FiUdnkp9V7SrYAvDfVNigmGrLwksitQfQ7o1CjVX7D9EZmJwRXg==
Raw Tx data:

Hash Comparison

Hash stored in database: 6b62cf9a4f51bbcadffc497fcbeb6f233765c9dcf567413e025e72f03b92c6ff

Hash from Mainchain Tx: 6b62cf9a4f51bbcadffc497fcbeb6f233765c9dcf567413e025e72f03b92c6ff

Dynamically generated hash: 6b62cf9a4f51bbcadffc497fcbeb6f233765c9dcf567413e025e72f03b92c6ff

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: