Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Joplin, Missouri

Aler Ronald Escobar-Velasquez, 36, from Joplin, Missouri, on 5 August 2021

Victim Info

  • Aler Ronald Escobar-Velasquez
  • Hispanic/Latino
  • 36
  • Male

Details

At 9:15 p.m., Webb City officers were called in response to a report of trespassing and illegal dumping. Upon arrival, officers encountered several people in a truck with a trailer. A fight allegedly occurred, and two officers were assaulted. During the fight, Aler Escobar gained control of an officer's Taser and allegedly began tasering the officer while the officer was on the ground. Escobar then allegedly attempted to gain control of the officer's duty weapon, and the officer shot and killed him.

Additional Evidence

  • Aler Ronald Escobar-Velasquez
  • 36
  • Male
  • Hispanic/Latino
  • Hispanic/Latino
  • Not imputed
  • 800 block East Fountain Rd
  • Joplin
  • MO
  • 64804
  • Jasper
  • 800 block East Fountain Rd Joplin MO 64804 Jasper
  • Webb City Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/08/Aler-Ronald-Escobar-Velasquez.jpg

Source

Source ID: 30718 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 63612. Submitted in Mainchain Tx 4EAB2259FA57C694D0FCC4FDEF9172EA598B4989C3FF212B8C074188AC787DD6, at block height 135655

Transaction details

Tx 4EAB2259FA57C694D0FCC4FDEF9172EA598B4989C3FF212B8C074188AC787DD6
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: Ahy2kvksVTgD3I+v5b8TP+1xbFmqOESX6jshVfBvsiA8iH5Qw4hxmjcyqz2qH5GKT87eoJZy25ZNV6bH7tUlQw==
Raw Tx data:

Hash Comparison

Hash stored in database: 4c8c891be135fb12282264837b7a048e1252e237cbfbc19e782c2028b7073d73

Hash from Mainchain Tx: 4c8c891be135fb12282264837b7a048e1252e237cbfbc19e782c2028b7073d73

Dynamically generated hash: a12a23baf53726a77c676d8f1928858ea719e84dbe5539c0172bc16567a1375a

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: