If your bridge transaction has been in a 'delayed' state for almost 48 hours, it's not normal, but it’s not unheard of either—especially during network congestion, contract upgrades, or validator issues. Typically, most bridge transactions complete within minutes to a few hours. When it takes this long, you should first check the bridge's status page (if available) or look up your transaction hash on a block explorer to confirm it's still pending. Sometimes, delays occur on the destination chain due to finality issues or relayer problems. You can try reaching out to the bridge’s official support channels (like Discord or Telegram), and in some cases, you might be able to manually re-submit or re-trigger the transaction from their UI if they offer that feature.

You can read more about how to handle delays and what options are available on the bridge’s documentation or support FAQ. Here's a helpful link to get started: Understanding Delayed Transactions in Cross-Chain Bridges

Optional transaction block you might use if the UI supports it:

# Depending on the bridge, re-trigger might look like this in the UI:
Click on "Retry" or "Resubmit" under your transaction entry.

Reaching out to the support team with your wallet address and transaction ID can often speed things up.

You'll need to wait until the bridge transaction status updates to 'ready to claim'. Unfortunately, there's no exact ETA for when this might happen, as it can vary depending on several factors. In some cases, the delay could be due to network congestion or technical issues on the bridge's end. It's best to wait