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.
cbd60433eeb8b43acb3a8cf1689230bf0ba8bc15f5e04a9a7d7413c2405c7df6
Both payments are on their chains and locked to the same secret hash bad724d3699e0ec87e3852e898c18ea670fd94dc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cbd60433eeb8b43acb3a8cf1689230bf0ba8bc15f5e04a9a7d7413c2405c7df6
- MakerPaymentSpent: b0dc05317a97c1c361993bbde36c84e7a9e4432bb7cc5bc4910781cc57233cb9
d3bb91943c1026f53040afa535821043320225a78afdbe40eda7370cd76a8371
Both payments are on their chains and locked to the same secret hash bad724d3699e0ec87e3852e898c18ea670fd94dc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d39eb9065933dcb023f9b1f4008fe7670e761a7e7948111547f6585a0db58578
- TakerPaymentSent · TakerPaymentReceived: d3bb91943c1026f53040afa535821043320225a78afdbe40eda7370cd76a8371
- TakerPaymentSpent: da03473139e846d30c711b9da1081bacd48b5f6e603874d09b1c1e6d99f7f87c
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.