Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,432
| Malbis, Alabama

Clint Dearman, 35, from Malbis, Alabama, on 18 July 2021

Victim Info

  • Clint Dearman
  • White/European American
  • 35
  • Male

Details

Police were searching for Dearman, who was wanted for being a person with a felony conviction in possession of a firearm. Police located Dearman's vehicle and tried to get Dearman to exit. Dearman reportedly attempted to get away, and police shot and killed him.

Additional Evidence

  • Clint Dearman
  • 35
  • Male
  • White
  • 29805 AL-181
  • Malbis
  • AL
  • 36526
  • Baldwin
  • Spanish Fort Police Department, Daphne Police Department, Baldwin County Sheriff's Office
  • AL0051300, AL0050800, AL0050000
  • Gunshot
  • Pending investigation
  • No known charges
  • No
  • Allegedly Armed
  • gun
  • other
  • car
  • yes
  • 7039
  • Suburban
  • Part 1 Violent Crime
  • involved in officer shooting, possesion of firearm with felony conviction

Source

Source ID: 9385 - 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 63780. Submitted in Mainchain Tx 8028D8E295D921B9496AC7A0460DC586FB69783439353C05EF3ECAFE63703BB6, at block height 136585

Transaction details

Tx 8028D8E295D921B9496AC7A0460DC586FB69783439353C05EF3ECAFE63703BB6
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: JeM9PPsTeYESrN+72+vgn6evMpGNlzriL8oM1oj45VdKMf2EEHHy4rgUO0XMqSnNKwpJ4lGB2DrqtiO7y14Lzw==
Raw Tx data:

Hash Comparison

Hash stored in database: d177016ca753327764e1cd8681c405a40868631e2a060047308ef27849fb3698

Hash from Mainchain Tx: d177016ca753327764e1cd8681c405a40868631e2a060047308ef27849fb3698

Dynamically generated hash: d177016ca753327764e1cd8681c405a40868631e2a060047308ef27849fb3698

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: