Four Checks for a Partially Filled Cross-Chain Transfer

A partially filled cross-chain transfer needs four checks: confirm the source transaction, verify the route, inspect destination activity and compare the amount received. A bridge moves value through steps on separate blockchains, so a confirmed send does not by itself prove the destination transfer is complete. Some bridges support partial fills; Across’s V3 documentation says its deposits are filled completely or not at all.

Did the source transaction confirm?

Start with the source-chain transaction hash in a block explorer for the network you sent from. Check that the transaction succeeded and that the token left the sending address; a pending or reverted transaction has not completed the first leg.

Keep the hash, source network, destination network, token and approximate send time together. Bridge status tools may need the source transaction hash or a deposit identifier to find the transfer. If the hash shows success but the bridge interface has not updated, check the explorer before submitting anything again.

Does the route match the transfer?

Compare the source and destination networks, token and receiving address with the original transfer details. A token can have different contract addresses on different chains, and a wallet may hide a destination token until it is added or the destination network is selected.

Fees and token conversion can also change the destination amount. For a closer look at how network and bridge costs affect a route, see this manta bridge explainer. Use the transfer’s own quote and status for its figures; a fee example from another route cannot establish what this transfer should deliver.

Has the destination leg actually completed?

Look for a destination transaction hash or a final status from the bridge’s tracker, then open that hash in the destination chain’s explorer. 0x’s cross-chain status documentation distinguishes a bridge in progress from a completed fill, and says a retry transaction hash alone does not confirm delivery.

If the tracker reports a pending state, the transfer may still be processing after the source transaction has confirmed. Wait for the bridge’s stated deadline or status guidance, and use the bridge’s support channel if that window passes without a terminal status. Do not treat a wallet balance display or a source-side success message as proof of destination settlement.

Does the amount received match the expected amount?

Compare the destination balance change with the transfer’s quoted output, accounting for the displayed fee and any swap. 0x documents that the settled amount can differ from the quote because of slippage, so the destination transaction and actual balance are the evidence of what arrived.

• Source: transaction succeeded and the intended input left the sending address.
• Route: destination chain, token and recipient match the transfer details.
• Destination: tracker status is final and the destination transaction is confirmed.
• Amount: received value is reconciled against output, fees and any swap.

If all four checks pass, the transfer is complete even if the wallet display needs refreshing. If only the source leg is confirmed, keep the transaction details and follow the bridge tracker until it reports delivery, refund or another final state.