> ## Documentation Index
> Fetch the complete documentation index at: https://docs.layerzero.network/llms.txt
> Use this file to discover all available pages before exploring further.

# LayerZero Tools Overview

> Step-by-step guide to layerzero tools overview using LayerZero V2. Build and deploy omnichain applications with crosschain messaging. Follow step-by-step de...

This section of the documentation covers **three** key resources that help developers inspect and integrate with LayerZero’s crosschain infrastructure.

Below is a summary of what each tool does and when you might want to use it.

## LayerZero Scan (UI)

The [**LayerZero Scan** overview page](./layerzeroscan/overview) explains the **web-based block explorer** that showcases:

* **Crosschain transactions** (messages) in a unified interface
* **Source/destination chain** details for any bridging operation
* **Individual transaction status** (delivered, pending, or failed)
* **Address search** to view bridging events associated with a particular user or contract

**Use it if**:

* You need a **visual** way to check crosschain TX status.
* You want to see real-time bridging volume or debugging info for your messages.

## LayerZero Scan Swagger API

The [**API** page](./layerzeroscan/api) documents the **Swagger-based** endpoints that expose the same crosschain transaction data as the web UI, but in a programmatic manner:

* `GET /messages/tx/{tx}` to fetch message details
* `GET /messages/wallet/{srcAddress}` to Retrieve messages initiated by a specific wallet address.
* Query-based endpoints to **filter** or **search** messages by chain, status, or time

**Use it if**:

* You want to **automate** crosschain transaction queries (e.g., in a custom dashboard).
* You need to **poll or monitor** message statuses at scale (like for bridging analytics or notifications).

## LayerZero Endpoint Metadata

The [**Endpoint Metadata** page](./endpoint-metadata) details a **comprehensive JSON** file that maps:

* **All known LayerZero chain deployments** (bridging contract addresses, RPC endpoints, etc.)
* **Token metadata** on each chain (addresses, decimals, pegging info)
* **DVNs** (Decentralized Verifier Network addresses), chain explorers, environment flags, and more

It also explains how you can:

* Programmatically configure bridging by reading the `deployments` or `tokens` fields.

**Use it if**:

* You want to ensure you have the latest official addresses rather than manually hardcoding them.

## Putting It All Together

* **LayerZero Scan** (web UI) → Quick visual debugging, real-time transaction lookup.
* **LayerZero Scan API** → Programmatic crosschain transaction data retrieval and stats.
* **Endpoint Metadata** → Full listing of chain configs, bridging contracts, and tokens for advanced integrations or dynamic UIs.

Consider each tool a different piece of the puzzle:

* The **Scan** explorer helps confirm if a bridging transaction arrived safely.
* The **Scan API** helps you build your own custom dashboards or monitoring scripts.
* The **Endpoint Metadata** ensures your application always references the correct bridging addresses, token definitions, etc., across all LayerZero-supported networks.

For more context on how bridging works under the hood, see the rest of our [LayerZero documentation](../home/intro).