Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,484
| Nashville, Tennessee

Michael Lynn Tucker, 48, from Nashville, Tennessee, on 1 April 2021

Victim Info

  • Michael Lynn Tucker
  • Black/African American
  • 48
  • Male

Details

Police were attempting to arrest Michael Lynn Tucker. Tucker was added to the state's most wanted list after he was accused of killing three people in Memphis on March 26. When police got to the door, someone inside fired at least three shots. Police said officers never fired back, but they did deploy tear gas at some point, but received no response. Tucker never spoke to negotiators. After 3 p.m., police breached the motel room and found Tucker dead on the floor from a self-inflicted gunshot.

Additional Evidence

  • Michael Lynn Tucker
  • 48
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 4311 Sidco Dr
  • Nashville
  • TN
  • 37204
  • Davidson
  • 4311 Sidco Dr Nashville TN 37204 Davidson
  • Metropolitan Nashville Police Department
  • Suicide
  • https://fatalencounters.org/wp-content/uploads/2021/04/Michael-Lynn-Tucker.jpg

Source

Source ID: 29947 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65096. Submitted in Mainchain Tx 08E18AEE3665383569AAAF533D535F1FFED8B13BEB69B212E2B2AEEDD7045D0E, at block height 139430

Transaction details

Tx 08E18AEE3665383569AAAF533D535F1FFED8B13BEB69B212E2B2AEEDD7045D0E
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: KW4B0AJcyDzcoe4UXyj0ybJHsdX0AnqMQsC5+epAYsADs2Dg7koCd4C2KifYnWROd5yP035JsaLhMK4PkwfKgg==
Raw Tx data:

Hash Comparison

Hash stored in database: e1ec8cd57f9b822acd7deca914d8c2878627bb8225dc7477976a174c422caf30

Hash from Mainchain Tx: e1ec8cd57f9b822acd7deca914d8c2878627bb8225dc7477976a174c422caf30

Dynamically generated hash: d752f8ba9e6da34a6525eb35133a7e09e263625a03acc97faf0f93f50343e85c

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: