Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,507
| Hinckley, Minnesota

Anthony Michael Legato, 25, from Hinckley, Minnesota, on 9 October 2020

Victim Info

  • Anthony Michael Legato
  • White/European American
  • 25
  • Male

Details

Deputies responded to a 911 call from the victim of an alleged domestic incident at the Grand Casino Hinckley. Deputies spotted the suspect's vehicle while on their way to the casino and pursued it. The suspect reportedly entered I-35, driving south in the northbound lane, and then stopped. One of the deputies fired their weapon, hitting the suspect. The suspect's vehicle rolled and crashed into an oncoming vehicle and then came to a stop in the median.

Additional Evidence

  • Anthony Michael Legato
  • 25
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • I-35
  • Hinckley
  • MN
  • 55037
  • Pine
  • I-35 Hinckley MN 55037 Pine
  • Pine County Sheriff's Office
  • Gunshot
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2020/11/Anthony-Legato.jpg

Source

Source ID: 28997 - Fatal Encounters

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 67492. Submitted in Mainchain Tx 3F03F5D9462DED88B2A0AD1D07C93E6E7332B30A32B9E4C72034411D014D4F88, at block height 145646

Transaction details

Tx 3F03F5D9462DED88B2A0AD1D07C93E6E7332B30A32B9E4C72034411D014D4F88
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: H/QOoQutR87M+TeVSm7fRTJH7lw8c8lKhHmoD6PSyeFr/6KW2EnuCXcNjqrYYFX42tlMeYP3JxcaajVTfW5Fow==
Raw Tx data:

Hash Comparison

Hash stored in database: d10ecf22c410c47340d1012905b366a3d873b487c2a86d78c43ad1cb519340b6

Hash from Mainchain Tx: d10ecf22c410c47340d1012905b366a3d873b487c2a86d78c43ad1cb519340b6

Dynamically generated hash: d10ecf22c410c47340d1012905b366a3d873b487c2a86d78c43ad1cb519340b6

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: