Quick Answer
To transfer DOT, confirm the recipient’s asset and network, enter the amount in a compatible wallet and review the fee before signing. After submission, use the transaction reference to check execution on the correct chain. A successful on-chain transfer and a hosted provider’s account credit are separate stages.
Prepare the Recipient and Sending Account
A normal DOT transfer begins with the recipient’s current receiving instructions. Open those instructions before choosing an amount, particularly when sending to an exchange or another hosted account.
Confirm the asset, supported network, receiving address and any provider deposit minimum. Then select the source account that holds transferable DOT on the matching chain.
If you still need a destination you control, use the Polkadot wallet and receiving-address guide. A portfolio screen alone may not identify the account that will sign the payment.
For an exchange deposit, work from the active order. An expired order or an address copied from an earlier exchange may have different payment conditions.
Check that the recipient is accepting deposits before proceeding. A functioning blockchain does not establish that a hosted account is ready to credit its users.
Enter the Amount and Review the Fee
Use the wallet’s Send or Transfer action for DOT, then paste the receiving address. Compare the destination with the original instructions after pasting.
Review and Sign the Transfer
A typical send sequence is:
- Select the source DOT account.
- Confirm the sending network.
- Paste and verify the recipient.
- Enter the amount the recipient should receive.
- Review the network fee and account-preservation setting.
- Sign with the account’s supported method.
- Save the transaction reference once the wallet submits it.
The official DOT transfer guide shows the fee-review and signing stages. Button names differ between wallets, so use the values and destination in the final confirmation as your reference.
Calculate What the Recipient Receives
As a hypothetical example, a transfer of 12 DOT with a displayed fee of 0.002 DOT requires 12.002 DOT available for that transaction, plus any balance the account must retain under the chosen transfer mode. The fee in this example is illustrative; read the actual preview.
A hosted sender may instead deduct its withdrawal fee from the amount entered. Check the “recipient receives” field rather than assuming its amount box uses the same convention as your self-custodial wallet.
If the wallet refuses to submit, use the pre-send DOT balance diagnostics. That guide covers account restrictions and failed previews; the steps below begin once a transaction has actually been sent.

Find the DOT Transaction in an Explorer
Open the transaction from the wallet’s activity view where possible. Its explorer link should point to the chain that processed the transfer.
Look for the execution result as well as block inclusion. A transaction can appear in a block and still show a failed result, so “found in explorer” is not enough to establish that the recipient received DOT.
Record these details:
- Transaction hash or extrinsic reference.
- Source and destination accounts.
- Asset and amount in the transfer event.
- Execution result.
- Block reference and finality information shown by the explorer.
Polkadot explorers may display an extrinsic index alongside the hash. Either can help locate the operation when it is paired with the correct chain.
For a DOT payment to an exchange, keep the service’s order ID separately. For example, a DOT to XRP exchange has a source DOT deposit and a later XRP payout, each with its own network evidence.
Separate Sending, Finality and Recipient Credit
Polkadot transaction time is one part of a payment’s full journey. A provider-managed withdrawal can spend time in the sender’s queue before any on-chain transaction exists.
Once broadcast, the chain processes the transaction and exposes its result. A hosted recipient can then apply its own crediting threshold and internal accounting.
Use the stage to decide where to investigate:
| Evidence you have | What to inspect next |
|---|---|
| Sender says “processing,” with no on-chain reference | Sender’s withdrawal status and release conditions |
| A reference exists, but cannot be found | Correct chain, complete reference and sender’s broadcast status |
| Explorer shows failed execution | Error details and the actual account balance change |
| Successful transfer to the expected recipient | Recipient’s deposit history, minimum and crediting policy |
Avoid resending simply because the receiving app has not refreshed. First establish whether the original payment succeeded and which party controls the next stage.
Resolve a Successful Transfer With Missing Credit
When the explorer shows a successful transfer, compare the receiving account and asset with the provider’s deposit instructions. A success result confirms the on-chain operation, while the provider decides whether that operation matches its supported deposit route.
Check the amount against the recipient’s minimum and confirm that deposits were enabled. If you used a different chain from the one it monitors, ask the provider about that specific transfer rather than attempting another payment.
Send support the public transaction reference, network, asset, amount and destination account. Include the provider’s deposit or order ID if it supplied one.
You can make the request concrete: “The explorer shows a successful DOT transfer on the selected chain to the address in my deposit instructions. Here is the reference; please check the account credit.”
If the transaction failed, the transfer amount and any transaction fee need separate inspection. Read the account events before deciding whether to retry or change the amount.
DOT Transfer FAQ
These questions cover records and follow-up actions after preparing a payment. Keep the original transfer details available until the recipient has acknowledged it.
Is a screenshot of the send screen enough to prove payment?
It can document what you intended to send. A public transaction reference and successful execution result provide stronger evidence of what the chain processed.
Can support cancel a finalized transfer?
A support team cannot simply reverse a finalized blockchain transaction. Contact the receiving party about a mistaken payment and provide its reference, without assuming recovery is available.
Should I use a wallet’s “send all” option for an exact exchange deposit?
Use it only if its final preview delivers the amount the order requests and the account effects are acceptable. An exact deposit should be checked against the recipient amount, not the label on the button.
