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.
e914d2777b52be76ec25e4cbe11b4cbf687f506fa88c135a90e3c7b95559c3e7
Both payments are on their chains and locked to the same secret hash 816a350c708f8202ef85e32b57865054cd4b7e3c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: e914d2777b52be76ec25e4cbe11b4cbf687f506fa88c135a90e3c7b95559c3e7
- MakerPaymentSpent: 722c0dc6bcca54b74457a01406bf9fa2086a7016971f2ad27ce292738bb5e06d
7aaccbf0bfe18451244387fab5d5b77157a2ab23d983b03edacc323b0ef8150b
Both payments are on their chains and locked to the same secret hash 816a350c708f8202ef85e32b57865054cd4b7e3c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 005652479600905d0dedfb058d8b4e88d7e40a4221ad17199859815ac612d84c
- TakerPaymentSent · TakerPaymentReceived: 7aaccbf0bfe18451244387fab5d5b77157a2ab23d983b03edacc323b0ef8150b
- TakerPaymentSpent: c273179b2ce0195711cb204e6153d28c2b19660ad4b27dba628ae01f8d7cddb6
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.