Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Salem, Oregon

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.

Additional Evidence

  • Natzeryt Layahoshua Viertel
  • 22
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • 400 block Ewald Avenue SE
  • Salem
  • OR
  • 97302
  • Marion
  • 400 block Ewald Avenue SE Salem OR 97302 Marion
  • Salem Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/04/Natzeryt-Layahoshua-Viertel.jpg

Source

Source ID: 29960 - 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 65074. Submitted in Mainchain Tx 7828CE2D0A6690FB76434A86EB7A3EC0271EBAE2B93109D09CF7622E51173B46, at block height 139408

Transaction details

Tx 7828CE2D0A6690FB76434A86EB7A3EC0271EBAE2B93109D09CF7622E51173B46
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: tZtWXqqDJLL7q8QYiuQh0jvrm03xI5LGmAcr9pMHi540NDDMziPVOL7KL04iMgind3re/LJg9Ob8BoNt8HbO2g==
Raw Tx data:

Hash Comparison

Hash stored in database: b9427cd10f4cd7aa59b2f44622dda0274a8ea901a1b42132ff0d22e178270d50

Hash from Mainchain Tx: b9427cd10f4cd7aa59b2f44622dda0274a8ea901a1b42132ff0d22e178270d50

Dynamically generated hash: b58f6cb72baf18be4cac0449319e0b7ba45faff82271e412a56d912a48cb2b3f

Hashes Match?
NO

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: