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.
d64ddf736a0b9daa0eefb6bdb88367eb9fdca4e1bcef990e364ac6c1bbc8e691
Both payments are on their chains and locked to the same secret hash 3af507e7823a0a8de5484452cae77a5f01d46237, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d64ddf736a0b9daa0eefb6bdb88367eb9fdca4e1bcef990e364ac6c1bbc8e691
- MakerPaymentSpent: b4b4dec91e708bded919dce3c8217634dfa8d59b0583e7b09017975576e7c976
5ccee7242fdab40523c8309b842e4a82f8bc737056eb596b148fe63472334102
Both payments are on their chains and locked to the same secret hash 3af507e7823a0a8de5484452cae77a5f01d46237, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4b44db667e476465ee1fbedc36de462a988aa3173865a66f42ee139d5f1856fc
- TakerPaymentSent · TakerPaymentReceived: 5ccee7242fdab40523c8309b842e4a82f8bc737056eb596b148fe63472334102
- TakerPaymentSpent: e19bf540f3ef03e24fdd1236e53fc1f2b9b549755ab64793aae5e8dda4cb88cc
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.