560 DOT was sent to the wrong address. Is there a way to retrieve it?
1 Like
The short answer is no.
Given that the fund receiver is an existing active account, as seen on Subscan, your best bet is to contact him and kindly ask him to send them back if they were not intended for him.
1 Like
How can I contact this account?
you can see that this account is using Binance, Subscan | AssetHub Polkadot Extrinsic Details maybe reach out to Binance and ask for contact information ?
2 Likes
You can make another transaction with a symbolic amount to that address and add a message to it by including data in the transaction details.
1 Like
If the address belongs to Binance (like someone mentioned), your only realistic option is to open a support ticket with Binance ASAP. Provide the tx hash, time, amount, and explain it was sent in error. No guarantees, but exchanges sometimes help.
1 Like
Were you able to solve it?
1 Like
0x0157e819b578506012d98acb11472c0d014874911b863680d772d842a148dbea
I can’t reach Binance support because they don’t recognize TXHASH.
May be try sending them the extrinsic number or the link to the transaction.
1 Like
Transaction hashes are not necessarily unique on Polkadot. You can share with them the chain (Polkadot Asset Hub) and extrinsic ID ( 11445893-2), or the Subscan link: Subscan | AssetHub Polkadot Extrinsic Details
1 Like
Strictly speaking, transaction hashes aren’t guaranteed to be unique anywhere… as hash collisions are always theoretically possible.
That said, I’m guessing the point @bill_w3f is trying to make here is the more “Polkadot-specific” nuance: the exact same extrinsic can, in some edge cases, be included more than once (e.g. a tx with nonce zero, that somehow removes the existencial deposit of the account). Sure, that can happen in theory.
In practice though, it’s vanishingly rare, and it’s not especially helpful for this discussion. The reality is that essentially all serious indexers key transactions by their tx hash. So if you paste a tx hash (for a tx which has been included into a block) into Subscan, it will give you the block height, the extrinsic index for that inclusion and all the other relevant info about the execution of that transaction.
So yes: if you have the tx hash, that’s sufficient in ~all real-world cases. The “well, technically…” corner case exists, but it’s mostly useful for winning trivia night, not really relevant to this discussion.
In this particular case, the following link https://assethub-polkadot.subscan.io/extrinsic/0x0157e819b578506012d98acb11472c0d014874911b863680d772d842a148dbea works perfectly fine. Also, that transaction can not be included ever again anywhere in Polkadot 
.
1 Like
When I share the link, it doesn’t proceed to the next stage. It needs to recognize the Txhash coin and its quantity. The worst part is, when I type “Txhash,” “DOT” doesn’t appear; instead, 10-15 different tokens show up.
I think this is something you will need to bring up with Binance support (or whichever exchange you are using). I don’t have any particular knowledge of how they do things.
The transaction was rejected because the wallet address wasn’t mine, but now the DOT is showing up in the txhash.
I accessed live support.
“I’m sorry for the situation you’re experiencing, sir. Believe me, I’ve checked many times for you, but I couldn’t find any transactions associated with any address linked to Binance.”
I guess there’s nothing I can do.
Transferring money and sending messages would be difficult for me, and I don’t think it would interest him.
Maybe he’ll see these messages.
I’m sorry to hear that! 
I hope that at some point you can get it sorted out. 