Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Celina, Ohio

Chad R. Rammel, 33, from Celina, Ohio, on 31 July 2021

Victim Info

  • Chad R. Rammel
  • White/European American
  • 33
  • Male

Details

About 4:08 a.m., Celina officers saw a blue, 2004 Acura run a stop sign. The officers pursued the car as it allegedly was swerving. The car continued when officers activated their siren. The car, later found to be driven by Chad Rammel, accelerated to speeds in excess of 95 mph. The officers reportedly discontinued the pursuit. A short time later, a report of a crash on Mud Pike Mercer County Central Dispatch. Ohio Highway Patrol and the Mercer County Sheriff's Office responded. It was the Acura Celina P.D. tried to stop. Rammel was killed.

Additional Evidence

  • Chad R. Rammel
  • 33
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • 4001 Mud Pike Road
  • Celina
  • OH
  • 45822
  • Mercer
  • 4001 Mud Pike Road Celina OH 45822 Mercer
  • Celina Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/08/Chad-R.-Rammel.jpg

Source

Source ID: 30716 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 63648. Submitted in Mainchain Tx CC17B62AC631FA054EC030C346AD15DE323FF599F973B8058C977956C5325825, at block height 135691

Transaction details

Tx CC17B62AC631FA054EC030C346AD15DE323FF599F973B8058C977956C5325825
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: ZEsQI8ZO+syOg0BsGy46W3wIbRt7uAQdEGSfFxzIYUFrZpwv1/hFskKT3pMRZF6NPvJy3itEjPSAVdjtITIG8Q==
Raw Tx data:

Hash Comparison

Hash stored in database: c1953811faf6fc2b4bf1c9306d61658bc3fa9b81f1c5215cd34120c234141c43

Hash from Mainchain Tx: c1953811faf6fc2b4bf1c9306d61658bc3fa9b81f1c5215cd34120c234141c43

Dynamically generated hash: 82b92acaff95794cad1ad41d0f6598f21188f8e85b5939ec3babbb3365a632a1

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: