Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,481
| St. George, South Carolina

Stephen B. Swears, 56, from St. George, South Carolina, on 14 April 2021

Victim Info

  • Stephen B. Swears
  • White/European American
  • 56
  • Male

Details

Stephen B. Swears was wanted out of West Palm Beach, Florida, in connection to a kidnapping. St. George PD who spotted Swears, and chased him. The 2013 Ford Mustang, which was being driven by Swears, was traveling south on Highway when it ran off the road, lost control, crossed into the northbound lane, and struck a 2012 Ford Fusion about 11:30 a.m. The driver of the Ford Fusion was taken to a hospital with injuries. Swears was killed in the crash.

Additional Evidence

  • Stephen B. Swears
  • 56
  • Male
  • European-American/White
  • European-American/White
  • Not imputed
  • Fox Run Rd & Hwy 15 S
  • St. George
  • SC
  • 29477
  • Dorchester
  • Fox Run Rd & Hwy 15 S St. George SC 29477 Dorchester
  • St. George Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/04/Stephen-B.-Swears.jpg

Source

Source ID: 30041 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64904. Submitted in Mainchain Tx 93FB376C4CE6FF9FBAA5C006F166C266B7D8B0EFF4976AC4FFD2091409248800, at block height 139238

Transaction details

Tx 93FB376C4CE6FF9FBAA5C006F166C266B7D8B0EFF4976AC4FFD2091409248800
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: jcYLbBuoGzr7Ov54Umx0KwP5Hg6WjrzCrbXIBp4DdXgYJGMXmYhWtxsANAkN0WcsYNbdJkwYln2y15yuQEyJJQ==
Raw Tx data:

Hash Comparison

Hash stored in database: dcb3db8c7e0eddb2a33b68a1d1d3296184f6f92c5b4736f0cb2d3dbc18cb4a4c

Hash from Mainchain Tx: dcb3db8c7e0eddb2a33b68a1d1d3296184f6f92c5b4736f0cb2d3dbc18cb4a4c

Dynamically generated hash: 4f667a1ef40ebe49a5e8e4bc778099922aac3adf7ecbac1417e678acc5e9a5df

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: