Bridge Monitoring

Bridge & Relay Monitoring

Inspect the CCIP relay status, follow the live mission-control stream, trace bridge transactions, and review the managed Mainnet, BSC, Avalanche, Avalanche cW, and Avalanche to Chain 138 lanes.

These pages collect the public monitoring, route, wallet, and topology surfaces that support Chain 138 operations and investigation.

Bridge Freshness Context

Recent transactions are close to the visible chain tip.

Use the transaction tip and last non-empty block below to distinguish a quiet chain from a broken explorer.

active

Timeline Summary

Latest block #4538152 was 1s ago. Latest visible transaction was #4538151 3s ago.

Visibility Signal

Use the block gap and the last non-empty block above to tell low activity apart from an indexing issue.

Open latest transaction block →Open last non-empty block →Latest visible transaction time: 4/29/2026, 1:43:50 PM

Chain head and latest indexed transactions are closely aligned.

Recent blocks contain visible transaction activity close to the head. Bridge relay posture is shown alongside the same explorer freshness model used on the homepage and core explorer routes. Based on public stats and indexed explorer freshness.

Head: directly reportedTransactions: directly reportedFeed: snapshot

Bridge Subsystem Posture

These bridge-facing subsystem signals show whether the limiting factor is public head visibility, transaction indexing, relay monitoring, or degraded freshness queries.

RPC head

operational

Updated 3s ago

reported · complete · high

Provenance: rpc

Transaction index

operational

Updated 3s ago

reported · complete · high

Provenance: tx index

Bridge relay monitoring

operational

Updated 2s ago

reported · complete · high

Provenance: mission control feed

Stats summary

operational

Updated 2s ago

reported · complete · medium

Provenance: composite

Relay Fleet

operational

6 managed lanes visible

Feed: Snapshot fallback

Chain 138 RPC

operational

Head age: 1.8s

Latency: 4ms

Last Check

2s ago

Public status JSON and live stream are both active.

Open status JSON ->

Mainnet cW

Chain 138 -> Ethereum Mainnet

operational

Profile

mainnet-cw

Queue

Processed

Failed

Last polled: 3s ago

Bridge: 0x2bF7...D7B5

Mainnet WETH

Chain 138 -> Ethereum Mainnet

operational

Profile

mainnet-weth

Queue

Processed

Failed

Last polled: 5s ago

Bridge: 0xF9A3...f939

BSC

Chain 138 -> BSC

operational

Profile

bsc

Queue

Processed

Failed

Last polled: 5s ago

Bridge: 0x886C...b78C

Avalanche

Chain 138 -> Avalanche

operational

Profile

avax

Queue

Processed

Failed

Last polled: 5s ago

Bridge: 0x3f8C...725F

Avalanche cW

Chain 138 -> Avalanche

operational

Profile

avax-cw

Queue

Processed

Failed

Last polled: 4s ago

Bridge: 0x6350...3C75

Avalanche -> 138

Avalanche -> Chain 138

operational

Profile

avax-to-138

Queue

Processed

Failed

Last polled: 5s ago

Bridge: 0x152e...0dE7

Mission-control live stream

Open the server-sent event stream that powers live relay and RPC monitoring.

Open SSE stream ->

Bridge status snapshot

Review the current relay health payload, queue posture, and destination summary.

Open status JSON ->

Reverse AVAX lane

Check the managed Avalanche cW burn-back lane to Chain 138 that now runs as its own relay service.

Review AVAX -> 138 lane ->

Bridge trace API

Resolve source and destination addresses for a bridge transaction through mission control.

Open trace example ->

Visual command center

Open the interactive topology map for Chain 138, CCIP, Alltra, and adjacent integrations.

Open command center ->

Routes & liquidity

Move from bridge health into route coverage, pools, and execution access points.

Open routes page ->