Qunzell Richard, 17, from Wichita, Kansas, on 22 November 2001
Victim Info
- Qunzell Richard
- Unknown
- 17
- Male
Details
11/22/2001: Qunzell Richard died after his car struck a tree while fleeing from a KHP trooper. Shortly before 8:30 p.m., the trooper tried to stop Richard's 1989 Pontiac for a traffic violation on I-135, but he reportedly turned onto Kellogg, exited into the business district and sped away. According to the patrol, the trooper ended the pursuit after a few minutes due to high speeds before the Pontiac then went out of control, veered across the street and struck a tree just outside Madill Carbide Inc. The front end of the car wrapped around a 2-foot-wide tree trunk. Two teenage passengers were treated and released. A third passenger was hospitalized in serious condition. https://drive.google.com/file/d/0B62PuBu1vKRLdm1UUHpRZVF3aTA/view?usp=sharingPrimary Evidence & Links
Additional Evidence
- Qunzell Richard
- 17
- Male
- Race unspecified
- European-American/White
- 0.636456695
- 1504 E Waterman St
- Wichita
- KS
- 67211
- Sedgwick
- 1504 E Waterman St Wichita KS 67211 Sedgwick
- Kansas Highway Patrol
- Vehicle
- Unreported
- No
- 2001
Source
Source ID: 1328 - Fatal Encounters
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 122518. Submitted in Mainchain Tx 06A1BE77BF13940BA181BD657182D1DC8A65CB2B7BC22FE957899F9AD294C175, at block height 285905
Transaction details
Tx 06A1BE77BF13940BA181BD657182D1DC8A65CB2B7BC22FE957899F9AD294C175
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: n1jm/U998HM6amEH/cVMxDs7drjZFOcZpRIYrkkx/hhkWBiC9nuz+PqQwn0C4OWPgzGMnGkAzXgXYEitsYX/rg==
Raw Tx data:
Hash Comparison
Hash stored in database: cea0b5a7288be9d3c8a503d82e30bac6ad42150fdea6e61c43b395346fee24ab
Hash from Mainchain Tx: 1656342017
Dynamically generated hash: cea0b5a7288be9d3c8a503d82e30bac6ad42150fdea6e61c43b395346fee24ab
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: