External transactions
Check original terms and the saved execution state.
Step by step
- Open Transfers. External and Custody are separate tabs and appear only when permitted. Status filters on the server; Search covers only the current page.
- Select a transfer to see the full sender/recipient address, exact amount, hash, UTC dates and recorded observation. Check history reads stored evidence.
- These are historical records, not a fresh network check or a balance. External provider finality does not establish accepted payment; an unknown custody outcome does not release a reservation.
- Available custody actions follow queue prerequisites and current permissions. Backend checks still apply. Nothing signs, relays or recovers automatically. More tools opens the full permitted operation list.
- On a phone, selecting a row moves focus to its details. Back to list restores focus to the selected row.
Prepare, sign and submit
A new transfer requires an active proved address on an active external Account, a supported network and explicit permissions. Open More tools, choose preparation and check source, full destination, asset, atomic amount and fee.
Preparation stores the original terms and exact payload for external signing. Independently verify those terms on your signing device. Submit only the signed result for that request. The platform does not request your private key.
The signed transaction and hash are stored before network submission. After acceptance, run the permitted observation step. Node acknowledgement only means that node accepted the transaction; inspect subsequent canonical history.
Changing recipient, amount, fee or expired payload is not a replay. Do not create a new Intent to bypass an unknown outcome. The current external profile provides no automatic cancellation or replacement.