HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Explorer & evidence

Why are the Hybrid hash and base-layer hash different?

3 min read

They identify different records. A Hybrid identifier locates the platform’s retained evidence; a base-layer hash refers to an external-chain transaction when one is published. The two should not be substituted for each other.

One journey can leave several records

Hybrid-Chain can retain evidence about a workflow while an external blockchain records its own transaction. Each system identifies its own record. The Hybrid reference helps locate the platform’s evidence; the base-layer reference identifies the transaction on the relevant external chain. Different values are therefore expected and are not, by themselves, evidence of a mismatch. The useful check is whether the published relationship between the records corresponds to the operation you intended.

Use the matching explorer

Open the Hybrid reference in Hybrid-Chain Explorer. Where a supported base-layer link is present, use the external chain explorer link for the underlying transaction. Compare its chain, asset details, destination, and execution status as appropriate. Do not replace the external reference with the internal one in a report simply to make the fields look consistent. Keeping the labels distinct helps both users and support teams avoid searching the wrong system.

Do not assume a one-to-one relationship

The relationship between business records, platform events, and external transactions depends on the workflow. Several recorded stages can relate to one external event, and an internal operation may not have an external transaction at all. Use the references actually supplied rather than inventing a mapping from similar timestamps or amounts. If an expected link is absent, describe it as missing evidence and investigate through the responsible account or provider workflow before concluding that the transfer succeeded or failed.

In plain language

Why several reference numbers can describe one journey

A business request, a payment-provider record, a Hybrid-Chain event, and an external blockchain transaction can each have their own identifier. These are not competing names for the same database row. They identify different parts of a journey, just as an order number and a parcel tracking number describe related but different records. Keep the relationship between them rather than overwriting one with another. A hash is a compact cryptographic fingerprint used to identify or commit to data; a UUID is another kind of record identifier. Neither should be interpreted from its appearance alone. Use the label beside it and the system that issued it. When asking for help, include the network and the type of reference as well as the value. This makes it much easier to distinguish a missing link from a failed operation and avoids searching an external chain for an internal reference.

In plain language

A public record is evidence with a specific scope

An Explorer record is closer to a receipt or an entry in a logbook than to a live control panel. It describes something published about a particular event, object, or process. Some entries include links that let you examine the earlier steps or the underlying transaction. A record can remain useful after it becomes old: it may establish what was recorded at that time. It does not necessarily describe what the system can do now. Look at the record type, network, time, source, and stated verification result together. Missing information means the public view cannot establish that fact; it is not a reason to invent a positive or negative result. Private account records may contain additional context that is deliberately absent from Explorer. This is why a screenshot is a starting point for investigation, while the exact record and its supporting references are much more useful for reaching a conclusion.

What to do next

Use the internal record link for Hybrid evidence and the external explorer link for the base-layer transaction.

Inspect transaction details ↗