CROSS-CHAIN TRANSACTION RESOLVER

Find out where your bridge transfer is.

Paste a transaction hash. BridgeResolve identifies the bridge, checks both chains and shows the next safe step.

READ-ONLY · PUBLIC ONCHAIN DATA

Wireframe route preview from source network through bridge to destination network

Trace transaction

No wallet connection · No signatures · No access to funds.

Read-only cross-chain transaction resolver Paste the hash. Understand the bridge.

SupportedBridgeRow

Supported bridge families

Arbitrum canonicalRead-only fixture
WormholeRead-only fixture
LI.FIRead-only fixture
RelayRead-only fixture

How it works

One hash, one normalized result.

1

Read public evidence

BridgeResolve starts with public transaction data and keeps the flow read-only.

2

Resolve the bridge

Registry-backed classifier evidence identifies a likely bridge family and route without live upstream keys.

3

Show the safe next step

The result normalizes status, confidence, evidence, warnings, and a single action.

Demo statuses

All six normalized states are represented.

CompleteConfirmed across source, bridge, and destination evidence.
WaitingThe bridge flow is valid, but more confirmations or a delay remain.
Claim requiredA destination-side claim or redeem step may be needed.
Refund in progressOfficial evidence points to a refund path.
Manual supportEvidence indicates an official support flow is the safe next step.
UnknownAvailable evidence cannot support a confident state yet.

Trust block

Read-only means read-only.

BridgeResolve never connects a wallet, requests signatures, asks for seed phrases, or accepts custody of funds.

FAQ preview

Before you trace

Can BridgeResolve move funds?

No. It only reads public data and points to official destinations when evidence supports it.

Does the MVP need RPC keys?

No. This block uses deterministic fixtures so the full flow works locally.

Why is evidence collapsed?

The primary result stays readable while technical details remain available for review.