Efren Gomez, 80, from San Tan Valley, Arizona, on 26 May 2021
Victim Info
- Efren Gomez
- Unknown
- 80
- Male
Details
Around 2 a.m., a husband and wife were having a fight over their impending divorce. The man, Efren Gomez, had a knife and scissors and was actively stabbing himself as deputies entered the home. Gomez allegedly became aggressive toward deputies, and lunged at them with the scissors, and one of the deputies shot and killed Gomez.Primary Evidence & Links
Additional Evidence
- Efren Gomez
- 80
- Male
- Race unspecified
- NA
- NA
- Thompson Road and Hunt Highway
- San Tan Valley
- AZ
- 85142
- Pinal
- Thompson Road and Hunt Highway San Tan Valley AZ 85142
- Pinal County Sheriff's Office
- Pending investigation
Source
Source ID: 30306 - Fatal Encounters
Cross References
This report has possible entries from multiple sources
- Washington Post -Efren Gomez, 80, from San Tan Valley, Arizona - shot on 26 May 2021
- Mapping Police Violence -Efren Gomez, 80, from San Tan Valley, Arizona, on 26 May 2021
- Mapping Police Violence -Efren Gomez, 80, from San Tan Valley, Arizona, on 26 May 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64430. Submitted in Mainchain Tx 7DF1EB12DA9D81A1ABBF6729FB4CA9434C69A02A1EF6E6F1CBCA0A0624DF1282, at block height 138000
Transaction details
Tx 7DF1EB12DA9D81A1ABBF6729FB4CA9434C69A02A1EF6E6F1CBCA0A0624DF1282
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: vpLATn6+/NxpRmfWoLOOP9YFfGJdDmvlYb08OyPV/a4vu66Ao6V89Ibe5W7SYqjWWOpBKiZ+uVoGBcK1Fj6IOw==
Raw Tx data:
Hash Comparison
Hash stored in database: 469f25b23e6eeb5eeba4d7081f129841f832fe048d5e764092de459ecd5c4fc3
Hash from Mainchain Tx: 469f25b23e6eeb5eeba4d7081f129841f832fe048d5e764092de459ecd5c4fc3
Dynamically generated hash: 3d519d122bb62f0e8e5fdd58ecad3ade951503d969bc0c0afdeedc8fbf923c1a
Hashes Match?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: