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.
956afcf758f29fc197b6790d039c415a375a07ab54a219c4425fe48bea5c6af2
Both payments are on their chains and locked to the same secret hash 42535cf62d0328b02d57b4a64b3e357553ff9162, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 956afcf758f29fc197b6790d039c415a375a07ab54a219c4425fe48bea5c6af2
- MakerPaymentSpent: bb356298d4563b2fe21dfb7c4f594944eb58f637b18f435bf4681e70d351b4b1
1bc4b36e01043cae89a678803353ce731c11e09ce0d4c395db7f75d03f8cf974
Both payments are on their chains and locked to the same secret hash 42535cf62d0328b02d57b4a64b3e357553ff9162, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2eee116839b41904f549d4f50f7e2122bbf94fd8531757bed273c6149d574126
- TakerPaymentSent · TakerPaymentReceived: 1bc4b36e01043cae89a678803353ce731c11e09ce0d4c395db7f75d03f8cf974
- TakerPaymentSpent: ad43265010512047cb831fd9cbe284e83744e453bb8fb27484263aa33fe52fe9
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.