Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,507
| Reading, Michigan

Oscar Herrera, 32, from Reading, Michigan, on 28 April 2021

Victim Info

  • Oscar Herrera
  • White/European American
  • 32
  • Male

Details

A deputy was called to a home on a complaint of a dog at large. When the deputy went to the home, the dog reportedly bit him, and he shot and killed it. The owner, Oscar Herrera, allegedly confronted the deputy with a knife, and the deputy shot and killed him.

Additional Evidence

  • Oscar Herrera
  • 32
  • Male
  • White
  • 6500 South Edon Road
  • Reading
  • MI
  • 49274
  • Hillsdale
  • Hillsdale County Sheriff's Office
  • MI3013000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • knife
  • other
  • not fleeing
  • Rural
  • https://fatalencounters.org/wp-content/uploads/2021/05/Oscar-Herrera.jpg
  • Other Non-Violent Offense
  • animal complaint

Source

Source ID: 9155 - Mapping Police Violence

Cross References

This report has possible entries from multiple sources

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64731. Submitted in Mainchain Tx 43F07E0B6DE31B2A5A8D44A1A7C562428B49E6E9E3D432DAF37585B24F9A2A58, at block height 139065

Transaction details

Tx 43F07E0B6DE31B2A5A8D44A1A7C562428B49E6E9E3D432DAF37585B24F9A2A58
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: y0L5qi18hrDCjjcbkAGI5I2XxmgDhS7J3B5zOLF7xuQnQxtrFAH0ZwIWomrdqxvuf6Tl4NRnvzdIeDhhQPFegA==
Raw Tx data:

Hash Comparison

Hash stored in database: c985111177e9d7dfc0b50786012d446e0a76e8d19894deb727a3d28731018b1d

Hash from Mainchain Tx: c985111177e9d7dfc0b50786012d446e0a76e8d19894deb727a3d28731018b1d

Dynamically generated hash: c985111177e9d7dfc0b50786012d446e0a76e8d19894deb727a3d28731018b1d

Hashes Match?
YES

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: