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.
0229ff7e9a1610840486198d67dc23436569db8246a63ba5064899bca4653ebc
Both payments are on their chains and locked to the same secret hash ea9763feeedf00c4c3ef6a249acea12594699b35, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0229ff7e9a1610840486198d67dc23436569db8246a63ba5064899bca4653ebc
- MakerPaymentSpent: dd9319e90d3a8f891ee7f2fb43584e7f24625c89bbe4c808af607a19145ae676
285d7e8da457316782bb61dcb2e2ac4696b7519234c2a6b02af22c550b7c464b
Both payments are on their chains and locked to the same secret hash ea9763feeedf00c4c3ef6a249acea12594699b35, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 19d6e75a2fcb6962c8448aa8a546ffbe4d523b0905cc2ba970cb2244a2f0d6dc
- TakerPaymentSent · TakerPaymentReceived: 285d7e8da457316782bb61dcb2e2ac4696b7519234c2a6b02af22c550b7c464b
- TakerPaymentSpent: 76827be423b6465f3da865e0ddb555fb55630c690c7eb01aa47d42f4ce77eb74
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.