Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,481
| Coquille, Oregon

Cory M. Orsenico, 32, from Coquille, Oregon, on 22 April 2021

Victim Info

  • Cory M. Orsenico
  • White/European American
  • 32
  • Male

Details

Cory Orsenico, 32, was reported multiple times for increasingly dangerous driving. When a trooper turned to pursue Orsenico, the two vehicles were involved in a minor collision before Orsenico again sped off. Orsenico travelled from the slow lane of the three lane highway to the fast lane, then crossed the double yellow line before colliding with the vehicle in the opposing lane. The occupants of the other vehicle, Dawn Adams, 54, and Jeffrey Adams, 78, were killed, as was Orsenico.

Additional Evidence

  • Cory M. Orsenico
  • 32
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • US-101
  • Coquille
  • OR
  • 97423
  • Coos
  • US-101 Coquille OR 97423 Coos
  • Oregon State Police, Bandon Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/05/Cory-M-Orsenico.png

Source

Source ID: 30097 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64784. Submitted in Mainchain Tx 61F399287E78733D60068DC4A316EF008F3C2617CE032CBC7926234596885B32, at block height 139118

Transaction details

Tx 61F399287E78733D60068DC4A316EF008F3C2617CE032CBC7926234596885B32
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: XJ3+id/TjdxE+v4RjxyR/3HvZv7BTLvRE2ewpuNsXxks/fGHgwikMV8WP+QB39cxZk+q3Os2O2FplaAFVLSb2g==
Raw Tx data:

Hash Comparison

Hash stored in database: 2ffc16b61c57393297cf33179421353927e7a34ebbd7217637f1b6f0096b04d8

Hash from Mainchain Tx: 2ffc16b61c57393297cf33179421353927e7a34ebbd7217637f1b6f0096b04d8

Dynamically generated hash: d7cce87be3b3ffc33bc9f8a0e0676e2d53bf08ebb6fc0d60f29e41fc5643415c

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: