Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Naches, Washington

Name withheld by police, from Naches, Washington, on 24 March 2021

Victim Info

  • Name withheld by police
  • Unknown
  • Male

Details

Officers were first called to a Taco Bell at about 5:10 p.m. for a report of a woman who had been assaulted. Officers found a 22-year-old woman at the restaurant who told them she had been assaulted by a former boyfriend who had stolen her car. She told police the 41-year-old former boyfriend showed up at her place of business and asked her for a ride and she complied. Soon after getting into the vehicle, the man asked her to pull into a parking lot and started to assault the woman and placed her hands in zip ties. She was able to open a door and run to the nearby Taco Bell where the doors were locked because of COVID-19. An employee let her in the restaurant, and the man took off in her vehicle. About 30 minutes later, Yakima Police spotted the vehicle, and a chase started. A Yakima County Sheriff's Deputy joined the pursuit and rammed the vehicle, but the chase continued. The suspect finally stopped the vehicle, pulled out a gun and shot and killed himself.

Additional Evidence

  • Name withheld by police
  • Male
  • Race unspecified
  • NA
  • NA
  • Old Naches Hwy and Cherry Lane
  • Naches
  • WA
  • 98937
  • Yakima
  • Old Naches Hwy and Cherry Lane Naches WA 98937 Yakima
  • Yakima Police Department, Yakima County Sheriff's Office
  • Suicide

Source

Source ID: 29883 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58838. Submitted in Mainchain Tx ED195551017104564CE4BC4F73E1132C87EA5876DE76449756BA457A7C9E6F8F, at block height 4908649

Transaction details

Tx ED195551017104564CE4BC4F73E1132C87EA5876DE76449756BA457A7C9E6F8F
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: lfSWktypZx5aMMtr9ocMvfp55FH4qcLc1vFDclbcuJ8Exh8gOnZK/tEccudP2jIMhEnRFBzxCiCqJDWTPovBTw==
Raw Tx data:

Hash Comparison

Hash stored in database: e62cf1fd83b190ece455cdf94612825bbfd7dc68e78ecdb7c28a0d44fa7ef9bf

Hash from Mainchain Tx: e62cf1fd83b190ece455cdf94612825bbfd7dc68e78ecdb7c28a0d44fa7ef9bf

Dynamically generated hash: 0b587b828ee73900104896ca78e83078416d99d8f6fe832ff48f88579b4178f5

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: