LogoLogo
  • ⏩Introduction
    • Hyperlane Introduction
    • Getting started
    • Why Should You Use Hyperlane?
  • Permissionless Interoperability
    • Overview
    • Deploy Hyperlane
    • Warp Routes
      • Deploy a Warp Route
      • Deploy a UI for your Warp Route
    • Modular Rollup Interoperability
  • Build With Hyperlane
    • Quickstarts
      • Messaging
      • Accounts
      • Queries
      • hyperlane-quickstart repo
    • Guides
      • Finding my messages
      • Automatically pay for interchain gas
      • Manually pay for interchain gas
      • Choosing an interchain gas paymaster contract
      • Unit testing
      • Specifying an ISM
      • V2 migration guide
    • Explorer
      • Debugging messages
      • Configuring PI Chains
      • REST API
      • GraphQL API
    • Troubleshooting/Developer FAQ
    • Example apps
  • APIs and SDKs
    • Messaging API
      • Send
      • Receive
    • Accounts API
    • Queries API
    • Warp Route API
    • Interchain gas paymaster API
    • Hyperlane App Framework
      • Example usage
        • HelloWorld
        • Interchain Token
      • Solidity SDK
        • HyperlaneConnectionClient
        • Router
      • NodeJS SDK
        • RPC Providers
        • Deployment
        • Interchain testing
        • Quoting gas payments
        • App Abstraction
    • Hooks API
      • Contract addresses
  • Protocol
    • Overview
    • Mailbox
    • Interchain security modules
      • Interface
      • Multisig ISM
      • Routing ISM
      • Aggregation ISM
      • Optimistic ISM
      • Wormhole ISM
      • Hook ISM
      • CCIP-Read ISM
    • Interchain gas payments
    • Staking and slashing
    • Agents
      • Validators
      • Relayers
      • Watchtowers
    • Warp Routes
    • Implementation Guide
  • Operators
    • Validators
      • Guide
      • AWS setup
      • Monitoring and alerting
    • Relayers
      • Guide
      • Message filtering
    • Agent keys
      • Hexadecimal keys
      • AWS KMS keys
    • Agent configuration
      • Configuration reference
    • Running with docker compose
  • Resources
    • FAQ
    • Glossary
    • Contract addresses
      • Permissionless Deployment Contract Addresses
    • Domain identifiers
      • Permissionless Domain Identifiers
    • Default ISM settings
    • Coming Soon: Hyperlane v3
    • Token sources & faucets
    • Latencies
    • Github
    • Discord
    • Website
Powered by GitBook
On this page
  • Searching for messages
  • Permissionless Interoperability
  • Debugging Messages
  • API Reference
  1. Build With Hyperlane

Explorer

Using the Hyperlane Explorer to find and track messages

PreviousV2 migration guideNextDebugging messages

Last updated 2 years ago

The can be used to find messages on any network with a Hyperlane deployment. Drill down into messages for more details about their properties and status.

Messages to/from will 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 a chain config.

Searching for messages

The supports searching for messages using any of the following values:

  • 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

To search, enter your query into the top search bar. You can use the Origin Chain, Destination Chain, and Time filter options to narrow down your search.

Permissionless Interoperability

The explorer UI and REST API can be configured to search for messages on any chain with a Hyperlane deployment. See Configuring PI Chains for details.

Debugging Messages

If you're trying to debug a problem with message delivery, the Debugging messages page has useful tips.

API Reference

The explorer's data can be accessed programmatically via the REST API or GraphQL API. The REST API is recommended because it exposes a simpler interface for message data.

Note, by default the explorer will only find message on . To view messages send to and/or from other chains, see Configuring PI Chains .

core Hyperlane chains
Hyperlane Explorer
core chains
Hyperlane Explorer
Explorer search bar