Hi,
Depending on the method of ingest, Checksums COULD be stored on dc.description.provenance
b.e.

Submitted by xxxxxxx xxxxxxxxx on 2011-07-09T16:25:55Z
No. of bitstreams: 1
benchmarking del e_gobierno Local.pdf: 4197752 bytes, checksum: 4ff1d1fb534662d9e3fad95e9a23db15 (MD5)||Made available in DSpace on 2011-07-09T16:25:55Z (GMT). No. of bitstreams: 1
benchmarking del e_gobierno Local.pdf: 4197752 bytes, checksum: 4ff1d1fb534662d9e3fad95e9a23db15 (MD5)
Previous issue date: 2011-05


Since this metadata field contains sensitive information (emails, names & Checksums)  by default is Hidden in normal dspace configurations, so, it is not exposed in item-full-view (only visible to adminitrators)

see dspace.cfg... and/or other   .cfgs, There are plenty of references about this "hiding"

metadata.hide.dc.description.provenance = true
oai.mets.hide-provenance = true
bulkedit.ignore-on-export = dc.description.provenance

And (Perhaps) a way to acomplish what you want, would be to transform dc.description.provenance,
Best luck

Emilio