How to Track a Cross-Chain Treasury Payout

To track a cross-chain treasury payout, follow the transaction your wallet signed through the source contract, the cross-chain message and the destination transaction. Your wallet history shows the source-chain transaction; it does not, by itself, show whether the payout completed on the destination chain. The exact contracts and message identifiers depend on the transfer system, so start with the transaction receipt and its emitted logs.

What does the wallet transaction prove?

The wallet transaction proves that the source chain processed a call, not that the recipient received funds on another chain. Find the transaction hash in your wallet, open it in an explorer for that chain, and check whether its receipt succeeded. Then inspect the decoded call and logs to identify the contract called, the token and amount, the destination chain, and the intended recipient. A successful receipt means the source-chain execution completed; it does not establish destination settlement.

Look in the logs for a message identifier or another protocol-specific reference. If the protocol emits one, use it to follow the message through its tracking interface or indexer. If it does not, the source contract, destination, recipient, amount and transaction time can help identify the matching record. For a comparison of the available omnichain transfer options for payouts, see the separate guide; the implementation determines which records you can follow.

How do you tell whether the payout settled?

Settlement requires evidence on the destination chain: find the destination transaction or execution record, check its receipt, and confirm the recipient’s token balance or transfer event. The destination transaction may be submitted by a relayer or executor rather than by the treasury wallet, so search by the message reference or destination contract instead of expecting the treasury address to appear as the sender.

A source transaction can succeed while destination execution is still pending or fails. The destination receiver may reject a message because of its own execution rules, even after the source contract has accepted it. A tracking page can summarize these steps, but the chain receipts and logs show what actually executed. Treat a message as completed only when the destination execution succeeds and the intended recipient receives the expected asset.

What should you record for treasury reconciliation?

Keep the source and destination evidence together. This makes it possible to distinguish a completed payout from a source-side submission that has not yet resulted in destination funds.

• Source chain, transaction hash, receipt status and treasury contract.
• Token, amount, intended recipient and destination chain shown in the source call or logs.
• Message identifier or tracking reference, if the system provides one.
• Destination transaction, receipt status and recipient transfer or balance change.

Compare the destination amount with the payout instruction, accounting for any explicitly configured fee or swap. If the destination transaction succeeded but the amount or token differs, reconcile against the destination transfer event and the system’s stated fee or conversion rules. The practical rule is simple: record the source submission, but mark the payout complete only after verifying the destination result.