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.
fad685c7059ffd4cd43b924ce51eca09d5c627a4a55cdd79561736ef37798a29
Both payments are on their chains and locked to the same secret hash ef2b043c91cbc3c152daa0a301becaac802e0af3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fad685c7059ffd4cd43b924ce51eca09d5c627a4a55cdd79561736ef37798a29
- MakerPaymentSpent: 1569e300746ab07d1775c4e5117247a15460d3006304466961b1a9f895d672bb
68fc83e37e94a2ebde83822973d3ba3d02605d29eb21d9ad94055f25dbabbc82
Both payments are on their chains and locked to the same secret hash ef2b043c91cbc3c152daa0a301becaac802e0af3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 716eef9918d7af50a7c5775af8796af1e657eb5a49d09840259ff9884137b7c6
- TakerPaymentSent · TakerPaymentReceived: 68fc83e37e94a2ebde83822973d3ba3d02605d29eb21d9ad94055f25dbabbc82
- TakerPaymentSpent: 65c8825139cf143d43d0db29b49344bc84d7ceebb0a3b9da094ea352d0265f3e
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.