Dewleen Self, 36, from Cleveland, Tennessee, on 2 April 2021
Victim Info
- Dewleen Self
- White/European American
- 36
- Female
Details
At approximately 1:16 a.m., Hamilton County Sheriff's deputies were involved in a vehicle pursuit that started on Highway 60. The pursuit was initiated after observing the suspect vehicle driving erratically leading a deputy to believe the driver was intoxicated. During the pursuit, the suspect vehicle traveled towards Rhea County and entered a boat ramp on Blythe Ferry Road. The suspect vehicle veered into the river off the side of the boat ramp causing the vehicle to flip upside down and become fully submerged in the river. The driver was taken into custody and notified deputies there was a passenger in the vehicle. Police initiated rescue efforts by entering freezing waters but quit because of the cold. The passenger, Dewleen Self, was found inside the vehicle dead.Primary Evidence & Links
Additional Evidence
- Dewleen Self
- 36
- Female
- European-American/White
- European-American/White
- Not imputed
- Blythe Ferry Road
- Cleveland
- TN
- 37312
- Bradley
- Blythe Ferry Road Cleveland TN 37312 Bradley
- Hamilton County Sheriff's Office
- Criminal
- https://fatalencounters.org/wp-content/uploads/2021/04/DewleenSelf.jpg
Source
Source ID: 29951 - Fatal Encounters
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65083. Submitted in Mainchain Tx C11EF668A6D71A1F20F0AD362C7EF48CCFA06AE61FFB44C26BE2EDBA373AE959, at block height 139417
Transaction details
Tx C11EF668A6D71A1F20F0AD362C7EF48CCFA06AE61FFB44C26BE2EDBA373AE959
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: EhRafyVYTkKtwlVvRRlmEUrhuGZVFOt3Ez3fwyVbpxB4PwKFoGsCZyr/Bc5kWcaGrNKMTfQaEF8QUm4kVVCW7Q==
Raw Tx data:
Hash Comparison
Hash stored in database: 717acdde3d0db80fedfada2972b55aceae5df0a618fb490125a5c4591e57e2f5
Hash from Mainchain Tx: 717acdde3d0db80fedfada2972b55aceae5df0a618fb490125a5c4591e57e2f5
Dynamically generated hash: 1c84bc2287f249bbf09a1c9739b4e545dd4f244baa5e7850090fbffaf89d858b
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: