Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Lake Los Angeles, California

Alfredo Aceves, 64, from Lake Los Angeles, California, on 29 April 2021

Victim Info

  • Alfredo Aceves
  • Hispanic/Latino
  • 64
  • Male

Details

Deputies were sent to the area of Rawhide Avenue and 170th Street East around 8:30 a.m. regarding an armed man. It was not immediately reported if he used the gun, but he allegedly pointed it a people. At least one deputy shot and killed Alfredo Aceves. Details as to what precipitated the killing were withheld by police.

Additional Evidence

  • Alfredo Aceves
  • 64
  • Male
  • Hispanic/Latino
  • Hispanic/Latino
  • Not imputed
  • Rawhide Avenue and 170th Street East
  • Lake Los Angeles
  • CA
  • 93591
  • Los Angeles
  • Rawhide Avenue and 170th Street East Lake Los Angeles CA 93591 Los Angeles
  • Los Angeles County Sheriff's Department
  • Pending investigation

Source

Source ID: 30131 - 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 64726. Submitted in Mainchain Tx D5FC36BF41515E47C351DF0B0C1A0AA3310874C0FB09495701DF4FCAC5912092, at block height 139060

Transaction details

Tx D5FC36BF41515E47C351DF0B0C1A0AA3310874C0FB09495701DF4FCAC5912092
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: FeaqUasrrAhd4TSp6b8pygXHXnuUyhWqT5SJTOJyGm5lMvn0y10zpcS/WHY6ihacehOuFNLwvreie594WjQaAA==
Raw Tx data:

Hash Comparison

Hash stored in database: b3ab9c485a3f5f2eb6fedef3729ea7ad4edcbd231c9e202b30eebce3b932f9ed

Hash from Mainchain Tx: b3ab9c485a3f5f2eb6fedef3729ea7ad4edcbd231c9e202b30eebce3b932f9ed

Dynamically generated hash: 39802035d00cf465bcadb9d8ea1f1a4da2d9914f58c5808156b96467e21b4a77

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: