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.
7ca456379d435b3d4189536de68d991be30b29887be2fe6f9f7585f7b090ccd2
Both payments are on their chains and locked to the same secret hash 7daa133bd170a9fe5f78d34e5187cfbab73e039f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7ca456379d435b3d4189536de68d991be30b29887be2fe6f9f7585f7b090ccd2
- MakerPaymentSpent: c8c591bcfc60f36741def530c0794c3416fd0ccaaf31a4691271353a3fdff302
3a11b446fababa82b981eceae49c724190e97e8262c6d2ff515590d9a784244a
Both payments are on their chains and locked to the same secret hash 7daa133bd170a9fe5f78d34e5187cfbab73e039f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bad9fbd35883fa099475f81861deb727eb2b368e8a48ebe13e15691bf6521112
- TakerPaymentReceived · TakerPaymentSent: 3a11b446fababa82b981eceae49c724190e97e8262c6d2ff515590d9a784244a
- TakerPaymentSpent: 34b1188a526ad25c69128ea874eca360dc87c715757209191d7e5ea3cd36fd4c
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.