Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 59,186
| Bloomington, Minnesota

Anton Lamont Burnes, 40, from Bloomington, Minnesota, on 18 March 2021

Victim Info

  • Anton Lamont Burnes
  • Black/African American
  • 40
  • Male

Details

Officers responded about 6:15 p.m. to a report of a man walking with a gun, and they found the man firing a handgun from the pedestrian bridge. A Bloomington officer fired his service weapon at the man, but it was not immediately clear whether he was struck by the gunfire. The man continued shooting his handgun from the pedestrian bridge for the next 10 minutes, but police did not return fire. Anton Lamont Burnes eventually climbed outside the bridge's safety fencing and shot himself, falling onto the I-494 below, killing himself.

Additional Evidence

  • Anton Lamont Burnes
  • 40
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 78th Street and Second Avenue
  • Bloomington
  • MN
  • 55420
  • Hennepin
  • 78th Street and Second Avenue Bloomington MN 55420 Hennepin
  • Bloomington Police Department
  • Suicide

Source

Source ID: 29833 - Fatal Encounters


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 58790. Submitted in Mainchain Tx D1CF66CABE2DE609F61DE4907BC5B630143FE466D5445FE5DBB1256F225C53B7, at block height 4849333

Transaction details

Tx D1CF66CABE2DE609F61DE4907BC5B630143FE466D5445FE5DBB1256F225C53B7
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: tendermint/PubKeySecp256k1
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: OnljQMv4BmatU5MISHedQtoVcA0Sl3qVCia64a8Wkbwh5URIRShQLV/CWE2yKGe21PE1BUYE5O71u86WRrn4ug==
Raw Tx data:

Hash Comparison

Hash stored in database: 3a06ec0b33bacb5df3a5ab95740e849b43a2ba96c8168a05438c9d7ab4818565

Hash from Mainchain Tx: 3a06ec0b33bacb5df3a5ab95740e849b43a2ba96c8168a05438c9d7ab4818565

Dynamically generated hash: 9170f7dd0521f793992bc518fc852c8aecf4825c13447a15b9b5b9bc059ca91b

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: