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.
6d718c3467d69e0c98b34eb8b6b1b820cde16aaa375b324948afa603e00465c9
Both payments are on their chains and locked to the same secret hash c04792e33779d20923f68f0228b46c07e639ec21, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 6d718c3467d69e0c98b34eb8b6b1b820cde16aaa375b324948afa603e00465c9
- MakerPaymentSpent: 6707336c42e5b6d73c285ef830944f26ee31bf7626ffdf2ee1898b6524f617cd
3effb795aa03f3cbe70f419c9db5506c21b5d793b6bc4170ae909862db77969e
Both payments are on their chains and locked to the same secret hash c04792e33779d20923f68f0228b46c07e639ec21, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6d08011a7d0ac563c63bcb28482586813c87b1b437df16fad87bb7492fdadab9
- TakerPaymentSent · TakerPaymentReceived: 3effb795aa03f3cbe70f419c9db5506c21b5d793b6bc4170ae909862db77969e
- TakerPaymentSpent: 904d232d2a60d09299a7f47b4469309717edcd20ac95ac4510b2183f846a885c
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.