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.
5228689d5813543dda3626b040b040b8c3abb539600c92d532d036c510869264
Both payments are on their chains and locked to the same secret hash 27c4d4efa3c20c19fd2cb415cf12cfe5c9fa97ee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5228689d5813543dda3626b040b040b8c3abb539600c92d532d036c510869264
- MakerPaymentSpent: 281778f10cc4b48d4f0f6c0b0bbcc61410b3d1dea23a228b1eb5499247a312d7
d141ee2f095eaafffb6daac6ac13b4e1fbcbc3e0e0fa63d62a6fe1e2d9301c0d
Both payments are on their chains and locked to the same secret hash 27c4d4efa3c20c19fd2cb415cf12cfe5c9fa97ee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 19ea4447834b9cac22525daf53d2d3fb5178c0137396e7b295e4b86d50b2aa36
- TakerPaymentReceived · TakerPaymentSent: d141ee2f095eaafffb6daac6ac13b4e1fbcbc3e0e0fa63d62a6fe1e2d9301c0d
- TakerPaymentSpent: cdbe0049c1dc1726e58a0686eba09ae09ed50bf11a57c666a7490a43eecd75be
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.