A delayed cBridge transfer can be traced to the stage holding it, so you can decide whether to wait, request a refund, or contact support. When a transfer stays pending past its estimate, start with the source transaction hash and the transfer status shown in the app.
Find the cBridge Stage That Has Stalled
The source explorer and the app status tell you where the transfer stopped. Look up the source transfer transaction on that network’s block explorer, then compare its result with the bridge status. An earlier token approval is a separate transaction; use the hash for the transfer itself.
-
Pending source transaction: Shows whether the transfer has entered a block and begun accumulating confirmations.
-
App transfer status: Separates submission, State Guardian Network confirmation, destination release, delay, and refund states.
-
Destination transaction: Shows whether a payout was executed after the source transaction succeeded.
Think of the route as collection, dispatch, and delivery: the source chain records the send, the State Guardian Network coordinates the cross-chain transfer, and the destination chain releases the asset. The analogy ends at a failed transfer, because a refund requires its own on-chain action rather than a parcel simply returning.
Resolve Source Confirmation and Transfer Failures
A pending source transaction calls for a source-chain fix; a transfer marked for refund calls for the refund flow. Read the explorer result first, because the same “pending” symptom can describe either stage.
Source transaction still pending. The explorer shows no confirmed block for the transfer hash. Wait for inclusion, or use your wallet’s speed-up option to replace the pending transaction with a higher gas price where the network supports it. Once it lands, allow the required source confirmations to accumulate. The requirement depends on the route, so follow the app’s status rather than assuming that one block completes the bridge transfer.
Source transaction succeeded, but the app still says “Submitting.” Compare the explorer’s block and success result with the app status. The bridge may still be processing the confirmed send. If the status stays there after the source chain has progressed, give support the source hash, source network, token, and destination network so they can locate the transfer.
Slippage exceeded your tolerance. In xLiquidity, the quoted destination amount can change as liquidity pools become imbalanced. When the required payout falls outside the tolerance selected for the transfer, the transfer fails. A status indicating “to be refunded,” with a bad-slippage reason where available, points to the next action: request a refund in the cBridge app. Wait for the refund transaction to be prepared, submit it with the sending wallet, and verify its confirmation on the source explorer. The refund transaction is the step that returns the assets to the source chain.
Test Destination Liquidity and Safeguards
A confirmed source send can still wait because the destination payout needs liquidity or must pass a contract safeguard. Match the app’s status to the destination token and contract before choosing an action.
Destination pool lacks liquidity. For an xLiquidity transfer, the destination pool must hold enough of the token to cover the payout. A bad-liquidity reason identifies this failure. Follow the app’s refund flow when the transfer is marked for refund; waiting for a different pool balance is not the refund action. For a later attempt, review the available amount and quote for the same route before sending again.
The token’s epoch volume cap has been reached. A destination contract can limit how much of one token it pays out during each epoch. At a busy time, earlier payouts may consume the remaining allowance. The next payout attempt then waits for a new epoch, even when its source transaction succeeded and the destination pool holds the token.
To test the cap, read the destination contract’s epochVolumeCaps, epochVolumes, epochLength, and lastOpTimestamps for the token. Compare the current epoch’s recorded volume plus your payout with the cap, using the token’s base units. A new epoch resets the accumulated volume; that is why waiting can resolve this hold. If your payout alone exceeds the cap, a new epoch leaves the same limit in place, so contact support with the transfer hash and contract values.
A delayed-transfer threshold is holding the payout. A large payout can enter a timed queue when its amount exceeds the destination contract’s token threshold. A “Delayed” status points to this case. Read the contract’s delay threshold and period, then wait for the release period to pass. The sgn-v2-contracts repository records these rules across the VolumeControl and DelayedTransfer safeguard contracts, including per-token epoch totals and queued payouts.
When the source succeeded and none of those signs matches, record the app status, both transaction hashes if available, and the destination token address. Those details let support distinguish a State Guardian Network confirmation wait from a destination release issue.
Related Questions
Can I cancel a cBridge transfer?
A source transaction that is still pending may be replaceable through your wallet on networks that support same-nonce replacement. Once the source transfer succeeds, follow its bridge status; use the refund flow when the transfer is marked for refund.
Where do I find my cBridge transaction on a block explorer?
Copy the source transfer hash from your wallet activity or bridge transfer record and search it on the source network’s explorer. For an Ethereum-to-Polygon transfer, start on Ethereum; search Polygon for a destination payout only after the source send succeeds.
Who should I contact about a stuck cBridge transfer?
Contact bridge support when a confirmed source transaction remains stuck without a matching refund or safeguard explanation, or when an eligible delayed payout remains unreleased. Include the source hash, route, token, amount, app status, and any destination hash.
The Celer bridge moves supported assets between networks through pooled liquidity or token mappings, and the route determines which destination balance and contract to inspect. The cbridge.finance gives you the cBridge site as context for the transfer whose status you are checking.
The deciding evidence is the last completed stage. Use the explorer and app status together to choose the next action: wait for confirmation or a timed release, request a refund for a failed transfer, or bring the recorded details to support.