Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Huber Heights, Ohio

Jalen T. Alexander, 19, from Huber Heights, Ohio, on 30 March 2021

Victim Info

  • Jalen T. Alexander
  • Unknown
  • 19
  • Male

Details

A chase began when the Troy Police Department attempted to initiate a traffic stop. Troy officers had been looking for a person with outstanding Miami County warrants. Instead of stopping, the Jeep fled, and officers pursued at high speeds. Officers attempted to stop the vehicle using stop sticks but failed. Police pursued until the Jeep crashed into a Volkswagen, killing the drivers 19-year-old Jalen Alexander and 32-year-old Chelsey Vollmer. A passenger in the Jeep received serious injuries.

Additional Evidence

  • Jalen T. Alexander
  • 19
  • Male
  • Race unspecified
  • NA
  • NA
  • US-40 & OH-202
  • Huber Heights
  • OH
  • 45371
  • Miami
  • US-40 & OH-202 Huber Heights OH 45371 Miami
  • Troy Police Department
  • Pending investigation

Source

Source ID: 29926 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65134. Submitted in Mainchain Tx CA2FB51C49ABC972F670235C9B02C42A2F44C71B26C502996FCC2CA988AEBDEB, at block height 139468

Transaction details

Tx CA2FB51C49ABC972F670235C9B02C42A2F44C71B26C502996FCC2CA988AEBDEB
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: ETqa7I8l4z83fo6NJx+yDIquz60Aj4rnXFd4QJ0OAQwQKQic6HZXW+C+YLjPew9z1EUBbSQ76dTo/XZDoker9w==
Raw Tx data:

Hash Comparison

Hash stored in database: afd03cccf5a4b2e6688f59746649c71443d06e066f168787eca99bf355bc252c

Hash from Mainchain Tx: afd03cccf5a4b2e6688f59746649c71443d06e066f168787eca99bf355bc252c

Dynamically generated hash: 72000d6b99ff6da26ad5d98f363bf27eac7b55c400c2df958b64150836ae85a5

Hashes Match?
NO

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: