Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,481
| Visalia, California

Ivan Cuevas, 27, from Visalia, California, on 31 March 2021

Victim Info

  • Ivan Cuevas
  • Hispanic/Latino
  • 27
  • Male

Details

Police received a call from a person who said there was a man with a knife threatening family members. The first officer at the house on North Conyer Street was confronted by Ivan Cuevas, who charged at him with a knife, and the officer shot and killed Cuevas.

Additional Evidence

  • Ivan Cuevas
  • 27
  • Male
  • Hispanic
  • North Conyer Street
  • Visalia
  • CA
  • 93291
  • Tulare
  • Visalia Police Department
  • CA0540700
  • Gunshot
  • Pending investigation
  • No known charges
  • Drug or alcohol use
  • Allegedly Armed
  • knife
  • other
  • not fleeing
  • Urban
  • https://fatalencounters.org/wp-content/uploads/2021/04/IvanCuevas.jpg
  • Domestic disturbance (family violence)
  • domestic disturbance

Source

Source ID: 8730 - Mapping Police Violence

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 65115. Submitted in Mainchain Tx 02E7F884700BBEA50E381017D6F943AF232EAF2BEA1962F08569EC66043D7918, at block height 139449

Transaction details

Tx 02E7F884700BBEA50E381017D6F943AF232EAF2BEA1962F08569EC66043D7918
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: veVYrEl3/ePskYcLI1EyN7OXRi4CSCa4+01AJsA0OKEyZW8fkRvet/KyrK6Gtc+C9YegpfUGCh2OqABk3hBtOg==
Raw Tx data:

Hash Comparison

Hash stored in database: 8c52bb3d69a77efc88019d942368b973baed29c15e799fb0fca4238612bc198e

Hash from Mainchain Tx: 8c52bb3d69a77efc88019d942368b973baed29c15e799fb0fca4238612bc198e

Dynamically generated hash: 8c52bb3d69a77efc88019d942368b973baed29c15e799fb0fca4238612bc198e

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: