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.
f9a4a2bc5182592089104d961261478d9640266fc88f9a1ca71b918a60d0fd21
Both payments are on their chains and locked to the same secret hash cfdbb823accf8a06be0946f098bc8340e0141b17, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f9a4a2bc5182592089104d961261478d9640266fc88f9a1ca71b918a60d0fd21
- MakerPaymentSpent: b2928c72f1d0b09d0725512de2ade17ee7b007a1359647e9fa52152e3c8696bc
56a709c8b3f258792fe9aa976dec35a385ea85674b3af700dce3ce5201807f25
Both payments are on their chains and locked to the same secret hash cfdbb823accf8a06be0946f098bc8340e0141b17, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 86020200768881bf89255b13f6f60a556f9b4a90b1a8669fb9fff2eab6fc333e
- TakerPaymentSent · TakerPaymentReceived: 56a709c8b3f258792fe9aa976dec35a385ea85674b3af700dce3ce5201807f25
- TakerPaymentSpent: e5aea4ac87ce86771517601954caee7f7f7561e45144528b02313370d700b10b
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.