We realized that we haven’t written anything on the Hyperlane Explorer before, so here’s a spotlight on the explorer and some new updates we just implemented!
What is the Hyperlane Explorer?
The Hyperlane Explorer enables users and developers to find extensive information about their Interchain Messages on the Hyperlane network. Track the delivery status of your message and get automated debug feedback. It also provides an API for easy access to message data.
Permissionless Interoperability support
We added support for Permissionless Interoperability to our Explorer, enabling anyone to add a custom chain to our Explorer. So any permissionlessly deployed chain can have an interchain message explorer out-of-the-box.
To view details about messages from PI chains, first configure the explorer with metadata about that chain. You can easily add any Hyperlane supported Chain to the explorer in Explorer’s Chain Settings. This will add the chain to the Explorer you are viewing locally, i.e. entirely client side, and lets you add any chain you would like!
For the latest information, refer to our documentation.
Interchain Gas Payment Support
The Hyperlane Explorer now shares information about the Interchain Gas Payments (IGP) for messages. It will also check the IGP payments for pending messages and report an error if the delivery is underfunded.
The goal is for you to be able to easily and quickly understand any issues arising relating to gas payments.
Searching for Messages
Messages to/from core chains are searchable by transaction hash, message ID, or sender/recipient address. For other chains, the explorer can be configured to search for messages by providing it with a chain configuration.
Our explorer supports searching for any of the following attributes:
- Hash of the transaction that initiated the message (origin tx)
- Hash of the transaction that delivered message (destination tx)
- Address of the account that sent the origin transaction
- Address of the account that sent the destination transaction
- Address of the message sender
- Address of the message recipient
- ID of the message
Our Explorer API provides endpoints to retrieve data about messages. Hyperlane agents collect useful information about activity on the system, including all messages. That data can be queried via the APIs. We provide these for free of charge without any required authentication for everyone.
Hyperlane Explorer offers different types of APIs depending on your experience as a Developer.
Both REST and GraphQL API serve similar data, the difference is that the data format returned by the Explorer REST API is a bit easier for developers to use. The GraphQL API can be used to get more information out of the message transfers but the information from GraphQL API has to be post-processed a bit in order to be fully usable. The Explorer is using GraphQL API internally. More features may be added to the Explorer soon but the GraphQL data will always be just raw data.
Connect your preferred GraphQL client or library to https://api.hyperlane.xyz/v1/graphql to query data!
The REST API is recommended over the GraphQL API because it exposes a simpler schema for message data.
Why not use Etherscan instead?
Etherscan and its derivative explorers only show you if a transaction was executed on the chain you are viewing, and do not have an interchain context. Hyperlane’s Explorer is specifically designed for interchain activity, and can provide you with information regarding the status of any interchain message sent via Hyperlane.
As always, please refer to our docs for up-to-date information!
More about Hyperlane
Hyperlane is the first Permissionless Interoperability layer, meaning anyone can bring the Hyperlane interoperability stack to any blockchain, any appchain, any rollup, anytime. With Hyperlane deployed on their chains of choice, developers can build Interchain Applications, apps that abstract away the complexity of interchain interactions and serve users on any connected chain. Additionally, Hyperlane’s modular security gives developers the power to customize their interchain security. Developers can mix, match, and stack security models, or even build their own. Explore the interchain in peace.
Hyperlane development is open-source and led by core developers at Abacus Works.