Tracking xCalls
Last updated
Last updated
Every xcall
is associated with a unique transferId
that can be used to track its lifecycle through a cross-chain transaction.
The easiest option to track an xcall
is by using to look up any transferId
. In the top right search box, enter the transferId
of interest.
Connextscan will pull up current status of the associated xcall
.
You can also query the on each chain to check the transaction status.
Make note of the transaction hash that interacted with the Connext contract.
Navigate to the hosted subgraph for the origin domain and query by the xcall's transaction hash or the transfer ID.
Navigate to the hosted subgraph for the destination domain and query by the transferId
obtained from the origin domain subgraph.
If there was a nested xcall
involved on the destination side, the executedTransactionHash
from step 3 can be used as the new origin-side transaction hash. To trace the nested xcall
, go back to step 1 using this executedTransactionHash
but instead consider the current destination domain as the origin domain.
XCalled
Transaction has been initiated on origin.
Executed
Funds have been delivered and calldata executed on destination, if applicable. If this happens before Reconciled, then this was a fast path transfer (non-authenticated).
Reconciled
Funds have been reimbursed to routers. If this happens before Executed, then this was a slow path transfer (authenticated).
CompletedFast
Transaction has been Executed and then Reconciled.
CompletedSlow
Transaction has been Reconciled and then Executed.