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

Funding & transfers

How do I view a Layer-1 token transfer in an external explorer?

3 min read

Where the record includes a supported base-layer transaction reference, use “Open in external chain explorer.” For a token transfer, the relevant explorer is the token’s underlying chain, not simply a site chosen from the token symbol. Internal Hybrid records remain separate.

Begin with the transfer record

Open the Hybrid-Chain transaction record and look for its base-layer reference. Where a supported external link is published, “Open in external chain explorer” takes you to the corresponding network’s transaction view. That view can show the external transaction and its execution details. Do not assume that the Hybrid hash is also the external hash; they identify different records. Keep both references if you are investigating the relationship between the platform record and the chain activity.

Tokens belong to a particular chain

A token symbol does not identify the correct explorer by itself. A token with the same symbol may be issued on several networks, each with a different contract and transaction history. Confirm the chain and token identifier before interpreting a search result. On a chain explorer, the transaction’s overall status and its token-transfer details can answer different questions. Check the intended recipient and amount as well as whether the transaction was included successfully.

What if no external link is shown?

The record may be internal, the base-layer reference may not be published, or the interface may not support a link for that network. A missing link does not establish either external success or external failure. Inspect the record type and available references, then ask for clarification if an external transfer was expected. Do not choose an explorer by guessing from the symbol or paste a private credential into a site offering to locate a transaction. Public transaction references are sufficient for public lookups.

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

The network is part of the address and asset

A currency symbol is a convenient label, not a complete destination. Two networks can use similar-looking addresses, and tokens with the same ticker can exist on more than one chain. The safe description includes the asset, its network, and any chain-specific token identifier, as well as the recipient address. Mainnet, Testnet, and Devnet are also separate contexts: a test balance is not a production balance simply because both screens show a familiar name. Before any external transfer, obtain the receiving details from the intended, authorized wallet workflow and compare the network at both ends. Do not choose a different network just because it appears cheaper without confirming the whole route. A shared application can make these choices easier to manage, but it cannot erase the differences between the underlying chains. If the destination or route is unclear, stop before authorizing the transfer and ask for clarification.

What to do next

Open the transfer details and check its base-layer hash and network. If no external link is available, do not treat the Hybrid hash as a Layer-1 transaction hash.

Browse transaction evidence ↗