Skip to content
DBIS ExplorerChain 138 Explorer by DBIS
Bridge

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

The chain head is advancing, but the latest visible transaction is older than the current tip.

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

low activityquiet chain
Timeline Summary
Latest block #6421978 was 2s ago. Latest visible transaction was #6420623 45m 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 →Block gap to latest visible transaction: 1,355Latest visible transaction time: 6/14/2026, 8:16:49 AM
The chain head is current, but recent head blocks are quiet — this is normal low-activity visibility, not a broken index.
Recent sampled head blocks are empty, which indicates a quiet chain rather than a broken explorer. 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: partial visibilityFeed: mixed

Bridge delivery mode

mode mixedUpdated 4s ago

Reason: Some freshness inputs are partial, so posture is reported conservatively.

Scope: Affects bridge monitoring and homepage summary surfaces.

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
operational
Updated 4s ago
reported · complete · high
Provenance: rpc
Transaction index
partial
partial
Updated 45m ago
reported · partial · high
Provenance: tx index
Bridge relay monitoring
degraded
degraded
Updated 4s ago
reported · complete · high
Provenance: mission control feed
Stats summary
operational
operational
Updated 4s ago
reported · complete · medium
Provenance: composite
Relay Fleet
degraded
6 managed lanes visible
Feed: Snapshot fallback
Chain 138 RPC
operational
Head age: 0.9s
Latency: 44ms
Last Check
4s ago
Public status JSON and live stream are both active.
Open status JSON ->
Mainnet cW
Chain 138 -> Ethereum Mainnet
operational
Profile
mainnet-cw
Queue
0
Processed
42
Failed
0
Last polled: 7s ago
Bridge: 0x2bF7...D7B5
Mainnet WETH
Unknown -> Unknown
configured
Profile
mainnet_weth
Queue
0
Processed
0
Failed
0
Last polled: Unknown
Bridge: Unspecified
BSC
Chain 138 -> BSC
operational
Profile
bsc
Queue
0
Processed
0
Failed
0
Last polled: 5s ago
Bridge: 0x886C...b78C
Avalanche
Chain 138 -> Avalanche
paused
Profile
avax
Queue
0
Processed
0
Failed
0
Last polled: 35s ago
Bridge: 0x3f8C...725F
Delivery disabled by policy
Avalanche cW
Unknown -> Unknown
configured
Profile
avax_cw
Queue
0
Processed
0
Failed
0
Last polled: Unknown
Bridge: Unspecified
Avalanche -> 138
Avalanche -> Chain 138
paused
Profile
avax-to-138
Queue
0
Processed
0
Failed
0
Last polled: 14s ago
Bridge: 0x152e...0dE7
Delivery disabled by policy

Config-ready lane health

LINK balances are read from each remote CCIP bridge contract. Proof-transfer status comes from operator-recorded CCIP message hashes when available.

Operator runbook: fund LINK with fund-ccip-bridges-with-link.sh · lane probe probe-bridge-lane-link-balances.sh · routing reference public API access

LaneOverallProofWETH9 bridgeWETH10 bridge
Defi Oracle Meta Mainnet (138)
chain 138
fundedproof-recorded
0xcacfd227A040002e49e2e01626363071324f820a
funded223.25 LINK
0xe0E93247376aa097dB308B92e6Ba36bA015535D0
funded242.25 LINK
Gnosis (100)
chain 100
degradedproof-recorded
0xc8656F24488cb90c452058da92d1a25BA464eaAE
degraded0.0291 LINK
0xa846aeAD3071df1b6439d5D813156aCE7C2c1DA1
degraded0.0291 LINK
Cronos (25)
chain 25
unfundedproof-recorded
0x3Cc23d086fCcbAe1e5f3FE2bA4A263E1D27d8Cab
unfunded0 LINK
0x105F8A15b819948a89153505762444Ee9f324684
unfunded0 LINK
Celo (42220)
chain 42220
degradedproof-recorded
0xAb57BF30F1354CA0590af22D8974c7f24DB2DbD7
degraded0.28 LINK
0xa780ef19A041745d353c9432f2a7f5A241335ffE
degraded0.28 LINK
Wemix (1111)
chain 1111
degradedproof-recorded
0xD3AD6831aacB5386B8A25BB8D8176a6C8a026f04
degraded0.26 LINK
0xa4B9DD039565AeD9641D45b57061f99d9cA6Df08
degraded0.26 LINK
Quick actions6 links · Show
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 ->