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.
37abbf3cc1595782faaf0001d83cda32026444398a82cdf51fc51e80104137e7
Both payments are on their chains and locked to the same secret hash 528a1b481743e60121ca95c8b72dc916b9d615d3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 37abbf3cc1595782faaf0001d83cda32026444398a82cdf51fc51e80104137e7
- MakerPaymentSpent: 260b171097cfd8c1c8802ede84b922077f00c76a60148f43b9a1512d05035b4e
3097507b5ff29c8f577fc83841ec81ec5fa20a6bbd0687deb8d7705682447486
Both payments are on their chains and locked to the same secret hash 528a1b481743e60121ca95c8b72dc916b9d615d3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 590823ed6a872c4fdd948040f43477dc1bdee694aa906b432151ba5e14ba7f7e
- TakerPaymentSent · TakerPaymentReceived: 3097507b5ff29c8f577fc83841ec81ec5fa20a6bbd0687deb8d7705682447486
- TakerPaymentSpent: f2f78533c28c1a332c25d427348bf8495d4524a8088688203be93602a79ee9ef
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.