An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
bc541709d2bb399cc6c079c8880e7e972a34dce53690b4c09e300dcc06dd5606
Both payments are on their chains and locked to the same secret hash 63e3d3ab0ca21d1ef9bbc603147dc5cb13c2399c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bc541709d2bb399cc6c079c8880e7e972a34dce53690b4c09e300dcc06dd5606
- MakerPaymentSpent: a457cff3ff8e0402700d5103429fddacaac189a063b76f2747012ee6e3563fd4
aa3d677f3ad25068f1425a865f2f8768f71194d4f4e4a2613b1417702f889ae3
Both payments are on their chains and locked to the same secret hash 63e3d3ab0ca21d1ef9bbc603147dc5cb13c2399c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 456d8c0b02ae5668c2fe38d5ed57ef971fb0f7a74a8c3ce80e8683f42b23e20e
- TakerPaymentSent · TakerPaymentReceived: aa3d677f3ad25068f1425a865f2f8768f71194d4f4e4a2613b1417702f889ae3
- TakerPaymentSpent: 9e1f7242395daf478c1c31935f6d7425e6975d8b2838872a84443a45e3de7a2f
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.