Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,469
| Huber Heights, Ohio

Chelsey R. Vollmer, 32, from Huber Heights, Ohio, on 30 March 2021

Victim Info

  • Chelsey R. Vollmer
  • White/European American
  • 32
  • Female

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

  • Chelsey R. Vollmer
  • 32
  • Female
  • European-American/White
  • European-American/White
  • Not imputed
  • US-40 & OH-202
  • Huber Heights
  • OH
  • 45371
  • Miami
  • US-40 & OH-202 Huber Heights OH 45371 Miami
  • Troy Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/04/Chelsey-R.-Vollmer.jpg

Source

Source ID: 29924 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65136. Submitted in Mainchain Tx 49EB1BCE68AA87808075E9B1473C890CCBC47BE01CD7CD443A560A0554EDAB51, at block height 139470

Transaction details

Tx 49EB1BCE68AA87808075E9B1473C890CCBC47BE01CD7CD443A560A0554EDAB51
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: boktuaMR1W5VWVQBsNsXtKAvvvJ47XUlJMeZ1z0StjJZ2nNlo4KEVKF6BmC5FK49UcEJE5F7Twli0X+S4mXDFA==
Raw Tx data:

Hash Comparison

Hash stored in database: 97a70e46e335f0e73636311694e7c9bf44f93fc1c2a368a1ba78e18b279b9995

Hash from Mainchain Tx: 97a70e46e335f0e73636311694e7c9bf44f93fc1c2a368a1ba78e18b279b9995

Dynamically generated hash: 4c30b4a4838e03e775e0d33f7ee5d96c9423347cfa403a3c8856349e4130b031

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: