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.
28557cb9cc8d1af168c85a5921e3638c8cd4b1871ba81d1188007f72a37d3f09
Both payments are on their chains and locked to the same secret hash 58f79502c571908fbeb32826c3ad6e4d713bd61d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 28557cb9cc8d1af168c85a5921e3638c8cd4b1871ba81d1188007f72a37d3f09
- MakerPaymentSpent: a133d2a77c83b5d3d4c8cbdf4730d942a7832a776c1e5aeb73604a26e9f38a6b
23782fd9eb475c432cfb626adb00690e865e5921a8f9646dc91c307f804a094c
Both payments are on their chains and locked to the same secret hash 58f79502c571908fbeb32826c3ad6e4d713bd61d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6a1905c2855eb1b6e0faca5e8326be75dcc83ca2f95817c70db6d84bb49ff969
- TakerPaymentSent · TakerPaymentReceived: 23782fd9eb475c432cfb626adb00690e865e5921a8f9646dc91c307f804a094c
- TakerPaymentSpent: 04037988f7823c9ed27d9b27b2355f9a8b0d2d924736b3e9b4dc411e05e90292
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.