Blockchain Verification

Verifying a Record

Authenticated users can verify any blockchain-anchored document from within the Vilulia platform. Verification confirms that the document has not been altered since it was anchored: the platform recomputes the SHA-256 hash of the current document and compares it to the hash recorded on the blockchain. A match means the document is unaltered; a mismatch means it has been modified since anchoring.

What you'll learn

How to verify an anchored record from within a case
What you need to perform verification (authentication required)
What a successful vs. failed verification means
How to look up a record by transaction hash or entity ID

Authentication requirement

All blockchain verification endpoints in Vilulia require authentication. There is no public verification URL where anyone can verify a document without logging in. To verify a document, you must be an authenticated user with access to the case in which the document was anchored.

Verifying from a case record

For arbitration awards, blockchain verification status is shown inline in the Awards tab of the case. Once an award is issued and anchored, the panel displays the transaction hash (tx_hash), block number, confirmed date and time, network name, and a link to view the transaction on PolygonScan. If an award has not yet been anchored, an Anchor on Blockchain button is shown. There is no separate Verification tab in the case record.

Verification by transaction hash or entity ID

Admins can look up any anchored record by transaction hash or entity ID from the Blockchain Verification History page in the admin dashboard. This page shows all anchored records in a filterable table and supports CSV export. It is useful when a third party provides a transaction hash and you need to confirm whether it corresponds to a record in your organization.

Verification results

A verified result means the SHA-256 hash of the current document matches the hash recorded on the Polygon blockchain at the time of anchoring — confirming the document has not been modified. A failed verification means the hashes do not match, indicating that the document content differs from what was anchored. A failed verification should be investigated immediately.

Can't find what you're looking for? Contact Support