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.
7904618f07da751cb3d5c3d3d75234a47b2541ac8cd16e2ac202d94f398b8ae9
Both payments are on their chains and locked to the same secret hash 3afea657f3fa7f4def4aba65b930fd27061a877c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7904618f07da751cb3d5c3d3d75234a47b2541ac8cd16e2ac202d94f398b8ae9
- MakerPaymentSpent: cbc04be449ebe5841d1a2b18b646209d2c77cc59aced4deabcb2344de7179921
726b340f0c3eb43f8a5f49e0173a6d870cce4f12ee2e80c5e1af18df391ad2d5
Both payments are on their chains and locked to the same secret hash 3afea657f3fa7f4def4aba65b930fd27061a877c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b20ee0da56c96f4c84aac8d91ae04e62f26e712d6ab76ecc67cdf4d4be9ae402
- TakerPaymentSent · TakerPaymentReceived: 726b340f0c3eb43f8a5f49e0173a6d870cce4f12ee2e80c5e1af18df391ad2d5
- TakerPaymentSpent: e6586e6cdf33975e08c0cfadac2b84e15de6fdb808ebd060f58d64ea62f1ccc0
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.