Natzeryt Layahoshua Viertel, 22, from Salem, Oregon, on 2 April 2021
Victim Info
- Natzeryt Layahoshua Viertel
- White/European American
- 22
- Male
Details
Police responded around 6:30 p.m. to a report that a suicidal man had injured himself. Firefighters arrived prior to officers, and the man allegedly threatened them with a firearm. When Salem Police officers arrived, Natzeryt Viertel allegedly confronted them while still armed. An officer shot and killed him.Primary Evidence & Links
Additional Evidence
- Natzeryt Layahoshua Viertel
- 22
- Male
- White
- 400 Ewald Avenue SE
- Salem
- OR
- 97302
- Marion
- Salem Police Department
- OR0240200
- Gunshot
- Pending investigation
- No known charges
- Yes
- Allegedly Armed
- gun
- other
- not fleeing
- no
- 6746
- Suburban
- https://fatalencounters.org/wp-content/uploads/2021/04/Natzeryt-Layahoshua-Viertel.jpg
- Mental Health/Welfare Check
- mental health crisis
Source
Source ID: 9072 - Mapping Police Violence
Cross References
This report has possible entries from multiple sources
- Fatal Encounters -Natzeryt Layahoshua Viertel, 22, from Salem, Oregon, on 2 April 2021
BEACON Data
Mainchain details
The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65071. Submitted in Mainchain Tx AD6F3A678C5541A3553395382AE87BE2A00E23E10B8160A6C5DB27877B0B316E, at block height 139405
Transaction details
Tx AD6F3A678C5541A3553395382AE87BE2A00E23E10B8160A6C5DB27877B0B316E
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: lOtWapf2UKa+UAVBXnmtliejqmGFm7act3Rkg4ei+swfURjN/r1zxScqmgnRoYh4FSaqYeZ1iqWi/xbCyGvy7w==
Raw Tx data:
Hash Comparison
Hash stored in database: 5cb040a32a19727c53e75c593b3af62caa8d222e511fe80b47fd0d13882152cc
Hash from Mainchain Tx: 5cb040a32a19727c53e75c593b3af62caa8d222e511fe80b47fd0d13882152cc
Dynamically generated hash: 5cb040a32a19727c53e75c593b3af62caa8d222e511fe80b47fd0d13882152cc
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: