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.
84abe3a43ea99913027cddfab0d698f38fae43be4eb768e1db50a5193b9a4db1
Both payments are on their chains and locked to the same secret hash 0e0e5416811e3cd9d79e6dabf8916db2deb256e0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 84abe3a43ea99913027cddfab0d698f38fae43be4eb768e1db50a5193b9a4db1
- MakerPaymentSpent: 20d1325d8b28a9ef14f604ef652c9d54af37a1da628cfeb755c6fe63b53dfbac
22f5893e1cb29058ef40b5d6a41246cff9917bb35d716c924958939db7876100
Both payments are on their chains and locked to the same secret hash 0e0e5416811e3cd9d79e6dabf8916db2deb256e0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4b90e9048c35155ca099bbaff1f723a27aeee54d21904f54f8a10126f05695e6
- TakerPaymentSent · TakerPaymentReceived: 22f5893e1cb29058ef40b5d6a41246cff9917bb35d716c924958939db7876100
- TakerPaymentSpent: 954c3007fc7b26ec5542c929b4d11450e1ae88e97cce33a902214c9e36cc05d8
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.