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.
3b051606dd2964b438dc2b300cf5e4799218cf4c43a98d431a63912bc312e45a
Both payments are on their chains and locked to the same secret hash a2006a04cd7ad58fe51bd5d07e7fd39a0a5d3d39, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 3b051606dd2964b438dc2b300cf5e4799218cf4c43a98d431a63912bc312e45a
- MakerPaymentSpent: 93365a8d75d72c6696de18e3542cd38c1875ede8f6683dfd55240f6fc7f8a85c
70941ed0efde8370582ce77ceb15e9c4f154a149d472aea4bac140d0803dfb29
Both payments are on their chains and locked to the same secret hash a2006a04cd7ad58fe51bd5d07e7fd39a0a5d3d39, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 63dd36d4f531240e79b4d1d9328ea6bb04f146d14977674a3893e4333e30c489
- TakerPaymentSent · TakerPaymentReceived: 70941ed0efde8370582ce77ceb15e9c4f154a149d472aea4bac140d0803dfb29
- TakerPaymentSpent: 39a600c3206b4771f3b6290b498b9a5631146c6f0c35feec1950367b16c07295
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.