Use an order ID, receipt, and blockchain transaction hashes to follow a route from source deposit to destination delivery.
An Order ID identifies the Sasquatch route and appears on the route receipt. A transaction hash identifies one blockchain transaction. Save both: the Order ID helps locate the route, while the source hash proves the deposit was broadcast.
Copy the Order ID from the receipt or Orders page. Copy the source hash from the wallet activity or the receipt. A destination hash appears after the provider broadcasts delivery on the destination network.
The source transaction moves the deposit from the sending wallet. The destination transaction delivers the output on another network. They can have different hashes, explorers, confirmation counts, and timestamps.
Deposit detected means the source transfer was found. Waiting for confirmations means the source chain has not reached the route requirement. Processing means the provider is executing the route. Destination transaction means delivery was broadcast. Completed means the route reports settlement. Delayed means the route needs more time or review.
Open Orders, enter the Order ID or public transaction hash, and compare the displayed network, asset, amount, and status with the saved receipt. Do not create a duplicate deposit while the original order is pending.
Use the source network explorer to confirm the deposit status and confirmations. After a destination hash exists, use the destination network explorer to confirm delivery. A wallet balance alone may lag or hide an unimported token.
Provide the Order ID, public source hash, public destination hash if available, route, amount, networks, timestamp, and screenshots. Never share a seed phrase, private key, wallet backup, or secret recovery material.
Cross-chain routes can have a source deposit transaction and a separate destination delivery transaction. Each belongs to its own network.
Requirements depend on the source network and provider. Use the active receipt rather than assuming one fixed number.
Switch to the destination network, verify the destination hash, and confirm that the correct token contract is visible in the wallet.
No. An Order ID and public transaction hashes are sufficient for investigation; never share recovery secrets.
