Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Wetumpka, Alabama

Jonathan Andrew Pears, 32, from Wetumpka, Alabama, on 28 July 2021

Victim Info

  • Jonathan Andrew Pears
  • White/European American
  • 32
  • Male

Details

Officers were called out around 6 p.m. to a domestic dispute. Jonathan Pears reportedly refused orders to drop a machete-like knife while walking toward deputies and Pears's father. A deputy shot and killed him.

Additional Evidence

  • Jonathan Andrew Pears
  • 32
  • Male
  • White
  • Timber Lane
  • Wetumpka
  • AL
  • 36093
  • Elmore
  • Elmore County Sheriff's Office
  • AL0290000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • machete
  • other
  • not fleeing
  • Rural
  • https://fatalencounters.org/wp-content/uploads/2021/08/Jonathan-Andrew-Pears.jpg
  • Domestic disturbance
  • domestic disturbance

Source

Source ID: 9480 - 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 63666. Submitted in Mainchain Tx D5FCBD501C0D1F110F750B553DCDF486C5D7AB6A0D8F22E5991D428A34951AF6, at block height 135709

Transaction details

Tx D5FCBD501C0D1F110F750B553DCDF486C5D7AB6A0D8F22E5991D428A34951AF6
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: R2qbP1alVMggiD6FAyhjOITrUOj0ufvBZ7Keo+NZgKdSrumDA3UruBkDwkeSdfMfkNYU1X5bO6b18GNLn21zxw==
Raw Tx data:

Hash Comparison

Hash stored in database: a9428c1c4e50f5227079514184260e8a5ad2139bc8388536ce129a177d6d8452

Hash from Mainchain Tx: a9428c1c4e50f5227079514184260e8a5ad2139bc8388536ce129a177d6d8452

Dynamically generated hash: a9428c1c4e50f5227079514184260e8a5ad2139bc8388536ce129a177d6d8452

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: