Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,432
| Temple, Pennsylvania

Stephen James Hughes, 62, from Temple, Pennsylvania, on 15 March 2021

Victim Info

  • Stephen James Hughes
  • Unknown
  • 62
  • Male

Details

At approximately 2:15 p.m. the Berks County Department of Emergency Services received a 911 call from a woman, reporting a man with a knife. She said he had threatened her, and the phone call disconnected. Muhlenberg Township police to a home and entered the residence. The woman said that Stephen James Hughes, with a knife, locked himself inside a second floor bedroom. Hughes brandished a knife, and one officer reportedly deployed his Taser to no effect. A second officer shot and killed Hughes.

Additional Evidence

  • Stephen James Hughes
  • 62
  • Male
  • Unknown race
  • 700 Wagon Wheel Lane
  • Temple
  • PA
  • 19560
  • Berks
  • Muhlenberg Township Police Department
  • PA0061300
  • Gunshot, Taser
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • knife
  • other
  • not fleeing
  • no
  • 6704
  • Suburban
  • Person with a weapon (knife)
  • Person with a knife

Source

Source ID: 8779 - Mapping Police Violence

BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65340. Submitted in Mainchain Tx C1F605FC72DEC808D6CFE14EB47C5CE6EF5775079CB8AB89D3AE62B67121B38A, at block height 140439

Transaction details

Tx C1F605FC72DEC808D6CFE14EB47C5CE6EF5775079CB8AB89D3AE62B67121B38A
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: d6hu7E2w34tPgZO6S6gxj+hWvO0EsB6MBpbQhzqMgswxeZcpxvmgKr2bRnn3GTbCg+wmq0Ybceml+aPd2xESyg==
Raw Tx data:

Hash Comparison

Hash stored in database: 4a75920370a817487631bcd2431375d49d18d971d113e80232660ea3cfaec8ba

Hash from Mainchain Tx: 4a75920370a817487631bcd2431375d49d18d971d113e80232660ea3cfaec8ba

Dynamically generated hash: 4a75920370a817487631bcd2431375d49d18d971d113e80232660ea3cfaec8ba

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: