Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,432
| Salina, Kansas

Kalun Purucker, 29, from Salina, Kansas, on 9 October 2020

Victim Info

  • Kalun Purucker
  • White/European American
  • 29
  • Male

Details

Police were looking for a man wanted in a KBI case and who had warrants for his arrest. The man got into a vehicle and the KBI agents and a Kansas trooper made a traffic stop at around 3:55 p.m. The driver stopped, and as they approached the car, the officers were fired upon. Two KBI agents and a KHP trooper returned gunfire hitting two men in the vehicle. Kalun Purucker was killed.

Additional Evidence

  • Kalun Purucker
  • 29
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • Cherokee Dr & Choctaw Ave
  • Salina
  • KS
  • 67401
  • Saline
  • Cherokee Dr & Choctaw Ave Salina KS 67401 Saline
  • Kansas Bureau of Investigation, Kansas Highway Patrol
  • Gunshot
  • Pending investigation

Source

Source ID: 28926 - 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 67502. Submitted in Mainchain Tx 32313598B56B8899431D519B412D489F0E4BF5C6F2394DEDBF75FD6A6C391FDE, at block height 145656

Transaction details

Tx 32313598B56B8899431D519B412D489F0E4BF5C6F2394DEDBF75FD6A6C391FDE
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: VlzEXx6jr5T6/udkiRTeOkVWs5iS3zibb81wEF1fXDg2XXY6yuyY8yZ/uxvnlnJI+7v/tx7lJdpgVuapTCSLOA==
Raw Tx data:

Hash Comparison

Hash stored in database: 0f491a03d027ce000386de18d9b7c6f1633077856da0026775e4ca73d6af60b1

Hash from Mainchain Tx: 0f491a03d027ce000386de18d9b7c6f1633077856da0026775e4ca73d6af60b1

Dynamically generated hash: 0f491a03d027ce000386de18d9b7c6f1633077856da0026775e4ca73d6af60b1

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: