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.
c7fb3af5587851c8cb33796cd970c1b569a4321ea67ca2636f901dbde24bc2e5
Both payments are on their chains and locked to the same secret hash 94a11114d680483b2c68cbfe53897e887d76a9fa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c7fb3af5587851c8cb33796cd970c1b569a4321ea67ca2636f901dbde24bc2e5
- MakerPaymentSpent: e67af14dd6a79905b83497b4b23caa6655bf7abfbd7170fc60c13fd7b12480f3
60cdaf1df47804650fdd9200c52142ac845d186c995e6655cde5c6d5a575afd2
Both payments are on their chains and locked to the same secret hash 94a11114d680483b2c68cbfe53897e887d76a9fa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6f042b4756ffb99c182c1c4f15ef1c1acbd0c33bd809bfd0c4e8825d61cbe70e
- TakerPaymentSent · TakerPaymentReceived: 60cdaf1df47804650fdd9200c52142ac845d186c995e6655cde5c6d5a575afd2
- TakerPaymentSpent: 719d7dde5bbb7242d609f180c79697205a83173fd0e9bc592b594e934895b979
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.