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.
201691b46b055f8a2b818f2e26ec3fedd21a60767ed070615d63b772ba3d0190
Both payments are on their chains and locked to the same secret hash c29c289b757754ffadfa8b3eaf58049037016d12, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 201691b46b055f8a2b818f2e26ec3fedd21a60767ed070615d63b772ba3d0190
- MakerPaymentSpent: 3f0432876f17e080a4ccfe478d144416a3bdb79e282f51a7ffb7f08f3fafa79e
3ac559da71717dc3791777495c73e641d345f819b4799dbbc407db9c9ea98fb0
Both payments are on their chains and locked to the same secret hash c29c289b757754ffadfa8b3eaf58049037016d12, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 02499b671202913c83ef4d989587304913a67d4a25e06745be6e912bcd0b9acc
- TakerPaymentSent · TakerPaymentReceived: 3ac559da71717dc3791777495c73e641d345f819b4799dbbc407db9c9ea98fb0
- TakerPaymentSpent: 51fea656da081dad257279961fd802836270b1a96e0890a2847926772859eaf6
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.