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.
ff76f7f09859593bf70902928b34db740b3d759060fb84d6ed5304d0d6f38873
Both payments are on their chains and locked to the same secret hash d4012e6e0d7275aea0e3cd34fd960d1a272aff06, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ff76f7f09859593bf70902928b34db740b3d759060fb84d6ed5304d0d6f38873
- MakerPaymentSpent: 2fb82d26bd1ab1a9ef434b554d6d7cf60bac59405dd86c44f191a26b41aafb5c
9175318d6a2587587a3c3b52ea45ea084e9d2a7ebdc1d5dd52a492e23f22b966
Both payments are on their chains and locked to the same secret hash d4012e6e0d7275aea0e3cd34fd960d1a272aff06, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a535f544bf42c6d7afbb797621478aba5b9ef213d433f56c5b8b0be414f05cbd
- TakerPaymentSent · TakerPaymentReceived: 9175318d6a2587587a3c3b52ea45ea084e9d2a7ebdc1d5dd52a492e23f22b966
- TakerPaymentSpent: acc49f834506ae505078986490cb969ae0c178bf65edf4881223b015ecf53589
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.