Jarred Kemp, 41, from Manhattan, Kansas, on 30 September 2020
Victim Info
- Jarred Kemp
- White/European American
- 41
- Male
Details
Following several calls for domestic disturbances regarding Jarred Kemp, who was experiencing a mental crisis and threatening family members, including firing a gun. He reportedly pointed a gun at a family member, and two officers shot and killed him.Primary Evidence & Links
Additional Evidence
- Jarred Kemp
- 41
- Male
- White
- 4600 Freeman Road
- Manhattan
- KS
- 66503
- Riley
- Riley County Police Department
- Gunshot
- Pending investigation
- No known charges
- Yes
- gun
- attack
- Not fleeing
- No
- 6210
- https://fatalencounters.org/wp-content/uploads/2020/10/JaredKemp.jpg
Source
Source ID: 8503 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Washington Post -Jarred Kemp, 41, from Lawrence, Kansas - shot on 30 September 2020
- Killed By Police -Jarred Kemp, 41, from Kansas on 30 September 2020
- Fatal Encounters -Jarred Kemp, 41, from Manhattan, Kansas, on 30 September 2020
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 67642. Submitted in Mainchain Tx E2F754B322EE479953F5EE1C2E19DA8274A6D1F6A1E4DCC64CD00B5AB83AD5B8, at block height 145796
Transaction details
Tx E2F754B322EE479953F5EE1C2E19DA8274A6D1F6A1E4DCC64CD00B5AB83AD5B8
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: /5TSqFid9/y0RoYr9OqvLIGYg7/oEG79gsQbeyWcnUkJO2NUYHIz2kI89JcQGEzNHUtCAbMsZBjyZhJ6SUIrfA==
Raw Tx data:
Hash Comparison
Hash stored in database: dc2fc2ba6f6599c2e7d48a9483f5bac892f0c244960f7120ab4d24b9f0411d12
Hash from Mainchain Tx: dc2fc2ba6f6599c2e7d48a9483f5bac892f0c244960f7120ab4d24b9f0411d12
Dynamically generated hash: 28ac280388d09e645c6060ae5181395c13b9d13b181a1e37124a07b48bcdf3ab
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: