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.
2c649b6989e6eb6c71e61d9bd145ef09eb255124ccef7d01cc8d4de60eb27e22
Both payments are on their chains and locked to the same secret hash 951b089517d36a6a67a362a8523ce59ae03805f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 2c649b6989e6eb6c71e61d9bd145ef09eb255124ccef7d01cc8d4de60eb27e22
- MakerPaymentSpent: fb6473149bf6854cc71cee4b1fd29b98a0eaad85e769e9826c15f58578921fd3
d162402e968dc8875a181d884eb356fff122c124b296dd324fcfbe19cb374809
Both payments are on their chains and locked to the same secret hash 951b089517d36a6a67a362a8523ce59ae03805f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4cbadcb47ec21123bc1c643bb425d5800aa6bd13e44c29cab6ecdf6d61ab2b8e
- TakerPaymentSent · TakerPaymentReceived: d162402e968dc8875a181d884eb356fff122c124b296dd324fcfbe19cb374809
- TakerPaymentSpent: 7cb84c048452637b6925b589076158f7712ba5d4397d44598859a3b3f18c3132
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.