Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Odenville, Alabama

Gerald Wayne Marlin Jr., 41, from Odenville, Alabama, on 20 March 2021

Victim Info

  • Gerald Wayne Marlin Jr.
  • White/European American
  • 41
  • Male

Details

St. Clair deputies were assisting ALEA with a chase that started on Hwy 231 in Ashville. The chase traveled Hwy 231 to Pell City turning on Hwy 174 towards Odenville. Odenville police, Margaret police and Argo police also pursued. The vehicle, driven by Gerald Wayne Marlin Jr. stopped after a spike strip was deployed.Marlin allegedly shot at officers, who shot and killed him.

Additional Evidence

  • Gerald Wayne Marlin Jr.
  • 41
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • US-411 & Hwy 174
  • Odenville
  • AL
  • 35120
  • St. Clair
  • US-411 & Hwy 174 Odenville AL 35120 St. Clair
  • St. Clair County Sheriff's Office, Odenville Police Department, Margaret Police Department, Argo Police Department, Alabama Law Enforcement Agency
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/04/Gerald-Wayne-Marlin.jpg

Source

Source ID: 29853 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58862. Submitted in Mainchain Tx 5CD359EBCE1B56AC4361FC78E88D50461E62260F4B17A4F40619078E6C9DE9F9, at block height 4908793

Transaction details

Tx 5CD359EBCE1B56AC4361FC78E88D50461E62260F4B17A4F40619078E6C9DE9F9
Sent from: und1n4axwtztv5fj70hd0fvy0q0vuaelzhhfms5063
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: ukWQpxYuMqCbcAqgcQeK7MVa/wTIMZ5Yh1ex90mYPSkenXo5PadXSvEnyjBSkEYm5CCZ8nD5z8L86E9034zJBw==
Raw Tx data:

Hash Comparison

Hash stored in database: f61bddc0d17117fe90cde6273a5639702d7029f9d90b06bbd09c1399d2dbaeec

Hash from Mainchain Tx: f61bddc0d17117fe90cde6273a5639702d7029f9d90b06bbd09c1399d2dbaeec

Dynamically generated hash: e1dc5e3cb4e356e21195709144c2847d039b6280fdcc92bfbc9fbd42547687a9

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: