A cross-chain transfer is stale when its tracking page is behind; it has failed when a required transaction did not complete. Check each blockchain record in order before deciding what to do.
A transfer has several separate stages
A cross-chain swap moves value from one blockchain to another and may exchange the asset along the way. Each blockchain keeps its own record, so the transfer does not appear as one transaction everywhere.
First, your wallet sends a transaction on the starting chain. A transaction hash, often called a “hash,” is its unique reference code. Once the starting chain accepts and confirms that transaction, a bridge or swap service can carry out the next part.
Some routes lock an asset on one chain and release or create a matching asset on another. Others use available funds on the destination chain and settle between providers later. The route determines which steps and records you should expect.
A delayed tracker does not prove a failed transfer
A tracking page can be stale if it has not caught up with the latest blockchain records. It may rely on an indexer, a service that gathers and organizes those records, and that service can update later than the blockchain itself.
For example, a service such as how quickswap swaps across chains handles a move and an exchange in one flow. The chains still record their own transactions, so a single progress view may lag behind one of those records.
Look up the starting transaction hash on an independent explorer, a website that displays public blockchain records. Check that the transaction succeeded and that it reached the required confirmations. Confirmations are later blocks added after the transaction; chains differ in how many are needed before a service acts.
Check the source before looking for a payout
The starting transaction decides whether the transfer can proceed. If it is marked failed or reverted, the requested action did not complete on that chain; check your wallet for any returned funds and do not assume the destination payment is coming.
If it succeeded, compare the recorded asset, amount, and destination address with what you intended. Then check the destination chain for an incoming payment, using the same address you gave the service. A different network can use a similar-looking address, so verify the chain as well as the characters.
For a bridge that sends a message between chains, the source transaction may be complete before the destination action is submitted. That message is an instruction, such as “release these funds.” A relay carries it onward, and the destination chain records a separate transaction when it acts on the instruction.
Take the next step from the first missing record
If the source transaction succeeded but no destination transaction appears, the gap is after the source step. Check the route’s stated expected time and whether the destination chain is processing normally. Some routes need extra confirmation time or a relay to submit the next action.
A common mistake is to start the same swap again because the tracker has stopped moving. First find the original source transaction and check whether it succeeded. Repeating a transfer could send the funds twice or create another exchange with a new price.
If the expected time has passed, keep the source hash, destination address, asset, and approximate start time together. Use the service’s official help channel to ask about the missing stage; never share your recovery phrase or approve a new transaction just because someone promises to release funds.
In short, follow the records from source to destination: a slow tracker can be stale, but the first missing or failed chain transaction shows where settlement stopped.