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.
361c9f7860cfedbab4e509a40be87e05fafe4b33dfe10c63d70bed4fe8969ac6
Both payments are on their chains and locked to the same secret hash 1c96b7fa5330e9f39c32a8ac56f413819766ccd5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 361c9f7860cfedbab4e509a40be87e05fafe4b33dfe10c63d70bed4fe8969ac6
- MakerPaymentSpent: 30e6692e043352a11850b21b7b4e3de48c459dc3c1f7ad829fd32aa4e05ca867
17c7fe4e960121f867fab6b675eaae7ba2c0c6e5fe8bc985df2b4acce9fd4f66
Both payments are on their chains and locked to the same secret hash 1c96b7fa5330e9f39c32a8ac56f413819766ccd5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6945b279460e7c23528ebc403881b8f66198d8a78b097f3c5a7185e64eca21e2
- TakerPaymentSent · TakerPaymentReceived: 17c7fe4e960121f867fab6b675eaae7ba2c0c6e5fe8bc985df2b4acce9fd4f66
- TakerPaymentSpent: 9860b0b8521f51bed5ddf262eeaa5215870e575d7583e0e32a0caf9ab9706043
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.