Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,469
| Palmetto, Georgia

Jamaal M. Willis-Powell, 30, from Palmetto, Georgia, on 2 April 2021

Victim Info

  • Jamaal M. Willis-Powell
  • Black/African American
  • 30
  • Male

Details

A Kia Forte with a burned-out headlight passed two deputies who were parked on the side of the road about 8:30 p.m. As one of the deputies pulled into the road, he allegedly saw the vehicle illegally pass a car that was stopped at a red light before turning right onto Collinsworth Road. In his report, the deputy noted the vehicle "appeared to already be fleeing from me before I activated my emergency equipment." The license plate on the car was registered to a different vehicle. The deputy activated his lights and siren, but the Kia sped away. The vehicle allegedly passed multiple cars by crossing double yellow lines and entering the opposite lane of travel, reaching speeds of up to 70 mph. Due to the speeds and nature of the roads, deputies were a short distance behind the fleeing vehicle and reportedly lost sight of it. Driver Jamaal Willis-Powell, 30, was trapped in the mangled vehicle. His passenger, Jasmine Simone Hayes, 28, was ejected from the car. Both were killed.

Additional Evidence

  • Jamaal M. Willis-Powell
  • 30
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • Fayetteville Road and Taylor Circle
  • Palmetto
  • GA
  • 30268
  • Coweta
  • Fayetteville Road and Taylor Circle Palmetto GA 30268 Coweta
  • Coweta County Sheriff's Office
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/04/Jamaal-M.-Wills-Powell.jpg

Source

Source ID: 29952 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 65082. Submitted in Mainchain Tx DE6F7356B17F54BCC5F723E06CB71A4F2BF290507B8DA5F3161675718692F17F, at block height 139416

Transaction details

Tx DE6F7356B17F54BCC5F723E06CB71A4F2BF290507B8DA5F3161675718692F17F
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: c/IL3bRT03pxWo+utgAbqUKqI9ml5c/QnBH3uY49ed9QLm3ug5tlPPDsbmB5iqUYqGFylnnOStlI4Q8WE5gW0A==
Raw Tx data:

Hash Comparison

Hash stored in database: 03847a739274e3a504cd227cd714522007a20680e6b32944e6cbe4d6f6ca5f2a

Hash from Mainchain Tx: 03847a739274e3a504cd227cd714522007a20680e6b32944e6cbe4d6f6ca5f2a

Dynamically generated hash: d46dbcf142005515634b3f7809925e1cc3144b3c1022811345e930f01858b905

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: