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.
83001adc25317af7c476f7964842822ced7a5df752ada41329434be17c3e1000
Both payments are on their chains and locked to the same secret hash 0ba8f2625edc04cf1468ac1b1b415d8599ee3ee6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 83001adc25317af7c476f7964842822ced7a5df752ada41329434be17c3e1000
- MakerPaymentSpent: 0446a4b4af4cd8287373a50628ddef053e83c783fd31d58235ee5e7746921012
97564f5f6c1e6be87d8bd5138130d134c947dba49c131106593acde95a115b53
Both payments are on their chains and locked to the same secret hash 0ba8f2625edc04cf1468ac1b1b415d8599ee3ee6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cc0838bcf128acf118fceeb565bd7708bb2d709b1c0a5a854c94275b21f89f12
- TakerPaymentSent · TakerPaymentReceived: 97564f5f6c1e6be87d8bd5138130d134c947dba49c131106593acde95a115b53
- TakerPaymentSpent: 2ab8d377f2f6bf477cc5497509d6ae80777793fbaec5950022832fd511e887df
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.