Public Accountability Chain Logo

Public Accountability Chain

Powered by Unification

Total incidents 64,469
| Nashville, Tennessee

Marvin Veiga, 32, from Nashville, Tennessee, on 24 April 2021

Victim Info

  • Marvin Veiga
  • Black/African American
  • 32
  • Male

Details

According to police, Officer Christopher Royer made a vehicle stop for a white Mercedes and ran the plate, but it did not match the vehicle description. The driver of the vehicle was cooperative, but a passenger got out of the passenger side with two butcher knives and rushed at Royer who shot and killed him.

Additional Evidence

  • Marvin Veiga
  • 32
  • Male
  • African-American/Black
  • African-American/Black
  • Not imputed
  • 3200 block Clarksville Pike
  • Nashville
  • TN
  • 37218
  • Davidson
  • 3200 block Clarksville Pike Nashville TN 37218 Davidson
  • Metro Nashville Police Department
  • Pending investigation
  • https://fatalencounters.org/wp-content/uploads/2021/05/Marvin-Veiga.jpg

Source

Source ID: 30096 - Fatal Encounters

Cross References

This report has possible entries from multiple sources


BEACON Data

Mainchain details

The BEACON hash was timestamped at and successfully submitted to Mainchain. The BEACON Timestamp ID is 64765. Submitted in Mainchain Tx F05F4B9E20F72C2E65EE082F968F4AA94620665AC41F83FF384135827DC7CF74, at block height 139099

Transaction details

Tx F05F4B9E20F72C2E65EE082F968F4AA94620665AC41F83FF384135827DC7CF74
Sent from: und1hf4jjflctvxcfxh5mc47yqvugwcugm9xzevszk
Public Key Type: /cosmos.crypto.secp256k1.PubKey
Public Key: A675rrH9WWpxIibCwaEs18WyVdsrByOXRqVay8/b8hGh
Signature: VTvk/XreEn6mkZaTzllAVnPvz9LdBflEqk1bpKJdeYJ9bnvS0S2QBp7BNHLMzfOoEB3FiJpryi64lG2OgzeAlQ==
Raw Tx data:

Hash Comparison

Hash stored in database: 9e6d95231390273ad762fbd94fcef61072f8a59fa4670f056fb97bb15f401826

Hash from Mainchain Tx: 9e6d95231390273ad762fbd94fcef61072f8a59fa4670f056fb97bb15f401826

Dynamically generated hash: e8806452e4e576d1b6a6ad8dd4e799019181ee58eb9275c32ed0636071dd0b39

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: