Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,460
| Wylie, Texas

Shawn Myers, 36, from Wylie, Texas, on 17 March 2021

Victim Info

  • Shawn Myers
  • Unknown
  • 36
  • Male

Details

Police received a report of a Ford pickup that had crash around 2:30 a.m. at a CVS. A Wylie officer was in the process of making an unrelated traffic stop at the CVS when a call came in about a report of a vehicle crash into a building. The officer responded to the crash and saw the body of a woman who had been seriously injured lying on the ground near the crash. A man, later identified as Shawn Myers, was also lying on the ground with a rifle. The officer ordered the man to disarm, and then shot and killed him.

Additional Evidence

  • Shawn Myers
  • 36
  • Male
  • Unknown race
  • 750 FM 544
  • Wylie
  • TX
  • 75098
  • Collin
  • Wylie Police Department
  • TX0430800
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • other
  • not fleeing
  • no
  • 6710
  • Suburban
  • Other
  • car crash

Source

Source ID: 8773 - 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 65311. Submitted in Mainchain Tx FAC7D82335B0D40584F5F064C04D0FE70FC23F3691FFCC5AFB68E89AEDD0A0C2, at block height 140410

Transaction details

Tx FAC7D82335B0D40584F5F064C04D0FE70FC23F3691FFCC5AFB68E89AEDD0A0C2
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: dFZxZfRGRJpWYUVnHuPu4z0w1smLuaM86ciFpTzdVKUjUEwlh7zA6c+SPkFy7ng002VWvwd2PELNJ0aWU2OwqA==
Raw Tx data:

Hash Comparison

Hash stored in database: f11269d5df9aac4f2b9bbccf980539419b2d6cd64cf1e4d0fc4e00cc6ff63f53

Hash from Mainchain Tx: f11269d5df9aac4f2b9bbccf980539419b2d6cd64cf1e4d0fc4e00cc6ff63f53

Dynamically generated hash: f11269d5df9aac4f2b9bbccf980539419b2d6cd64cf1e4d0fc4e00cc6ff63f53

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: