Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,432
| Bonnieville, Kentucky

James Horton, 42, from Bonnieville, Kentucky, on 17 November 2020

Victim Info

  • James Horton
  • Unknown
  • 42
  • Male

Details

A deputy tried to conduct a traffic stop in McDaniels, Kentucky, at about 9:50 p.m. During the stop, the driver allegedly shot the deputy, ran away and stole a pickup truck. Just after midnight, troopers in Grayson County spotted the stolen vehicle in the community of Wax, Kentucky. A pursuit began and went into Hart County. Troopers said James Horton fired a gun multiple times at police during the chase. The pursuit ended north of Bonnieville, Kentucky, where the pickup went off the road. Police said the driver got out of the vehicle with a gun, and a trooper fired, killing Horton.

Additional Evidence

  • James Horton
  • 42
  • Male
  • Race unspecified
  • NA
  • NA
  • KY-728
  • Bonnieville
  • KY
  • 42713
  • Hart
  • KY-728 Bonnieville KY 42713 Hart
  • Kentucky State Police
  • Gunshot
  • Pending investigation

Source

Source ID: 29182 - Fatal Encounters

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 66751. Submitted in Mainchain Tx B09B51BE5C1958FD66CC7905FD9ADD8BBFAE2817EB4C2DFD571F2CA3E3EE1323, at block height 144141

Transaction details

Tx B09B51BE5C1958FD66CC7905FD9ADD8BBFAE2817EB4C2DFD571F2CA3E3EE1323
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: kpDmun8stmppOS0h+lbN61nHgpm7GYg5B//jPFgOJ+A7yzwNEriMfwcrRFBDExk2NwnVZ3V+/C5NbqubbSAf+g==
Raw Tx data:

Hash Comparison

Hash stored in database: fbf58ce19a0d58c8293350a1d7195e3aef3233e59576b7d42cedbde66ca04b02

Hash from Mainchain Tx: fbf58ce19a0d58c8293350a1d7195e3aef3233e59576b7d42cedbde66ca04b02

Dynamically generated hash: fbf58ce19a0d58c8293350a1d7195e3aef3233e59576b7d42cedbde66ca04b02

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: