Nicholas Cory Kausshen, 41, from Spokane Valley, Washington, on 22 November 2020
Victim Info
- Nicholas Cory Kausshen
- Unknown
- 41
- Male
Details
A deputy attempted to stop a vehicle at about 6:45 p.m. after reportedly seeing reckless and erratic driving. Rather than stopping, the driver, Nicholas Cory Kausshen, fled, and the deputy chased him. Nicholas Cory Kausshen continued to drive recklessly, hitting parked cars and driving into opposing lanes of travel. A deputy attempted to immobilize the car using his patrol vehicle. Both vehicles sustained damage. Kausshen drove toward another marked patrol car and two deputies, and one deputy shot and killed him.Primary Evidence & Links
Additional Evidence
- Nicholas Cory Kausshen
- 41
- Male
- Unknown race
- Sprague Ave. and University Rd.
- Spokane Valley
- WA
- 99206
- Spokane
- Spokane County Sheriff's Office
- Gunshot
- Pending investigation
- No known charges
- No
- vehicle
- attack
- Car
- No
- 6327
- Suburban
Source
Source ID: 8643 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Fatal Encounters -Nicholas Cory Kausshen, 41, from Spokane Valley, Washington, on 22 November 2020
- Killed By Police -Nicholas Cory Kausshen, 41, from Washington on 22 November 2020
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 66666. Submitted in Mainchain Tx 9F117782B46DC80C18C5A9FF65F666FEC01C0F8C98976FD33BCDD0B4863AE85A, at block height 143293
Transaction details
Tx 9F117782B46DC80C18C5A9FF65F666FEC01C0F8C98976FD33BCDD0B4863AE85A
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: koSFfBA1+GLrsqQ5izPNL5AXc6XgKyEi/dz4CwMIRvpVoF1irHiuMf4lxUjbQYg+uqcT82AAaEGU/+NnV/KZdw==
Raw Tx data:
Hash Comparison
Hash stored in database: 3c69b8ed86edc97ec4fef91550554755daca55dab41e78d92e1b6c62ecc2c0c2
Hash from Mainchain Tx: 3c69b8ed86edc97ec4fef91550554755daca55dab41e78d92e1b6c62ecc2c0c2
Dynamically generated hash: 5b0a9d03f8a05f79b1a215ef3bb45bd43a2a3e95be43e0244dc0c24318451166
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: