Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Kimberling City, Missouri

Timothy Jonas Johnson, 33, from Kimberling City, Missouri, on 12 March 2021

Victim Info

  • Timothy Jonas Johnson
  • Unknown
  • 33
  • Male

Details

Kimberling City Police Department got a call around 10 a.m. about a burglary in progress. A man went into an condo that was empty at the time, fired off some gunshots, and went back to his own condo. The resident of the condo returned and saw the front door of the condo open and damage done inside. The man went downstairs into another room, and the Stone County Sheriff, Kimberling City Police and MSHP responded. There was a second person in the apartment with the alleged gunman. Timothy Jonas Johnson reportedly fired multiple shots, and one trooper shot and killed him.

Additional Evidence

  • Timothy Jonas Johnson
  • 33
  • Male
  • Race unspecified
  • NA
  • NA
  • Anchors Point Lane
  • Kimberling City
  • MO
  • 65686
  • Stone
  • Anchors Point Lane Kimberling City MO 65686 Stone
  • Missouri State Highway Patrol
  • Pending investigation

Source

Source ID: 29795 - 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 58767. Submitted in Mainchain Tx 1EE8E901093B2D29897B822A7F0DA31AF328FB478A2A0C9C358518EDDCBD2256, at block height 4819871

Transaction details

Tx 1EE8E901093B2D29897B822A7F0DA31AF328FB478A2A0C9C358518EDDCBD2256
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: 0Aq7xb8zOoQjLYHF+FmEHeWmVKoIIwrxOsZzJTzII41tkal9KoT+Anu6A4GT/q6FBfS3hLNhIs7wL1Aa9G1fTw==
Raw Tx data:

Hash Comparison

Hash stored in database: fd9c0acfc7c2ebe3b866d705e9d7830e862788847f9941f7ed55de159000eb14

Hash from Mainchain Tx: fd9c0acfc7c2ebe3b866d705e9d7830e862788847f9941f7ed55de159000eb14

Dynamically generated hash: 637e48a3a5239918859e62b82953912ade593bdb5b8d2bfb118397ec6c4a611f

Hashes Match?
NO

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: