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.
379f3705c7e061d4e9d2d2813a2ee7aeb8e0db441cb9c864be18d5974745a288
Both payments are on their chains and locked to the same secret hash f4672cd9ebc9f3badf5a506cb73f09ed0f1efa09, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 379f3705c7e061d4e9d2d2813a2ee7aeb8e0db441cb9c864be18d5974745a288
27861c45e6d17689a1e47b292379603439a3132ba2a1a66fb3e32ad7fee9cce3
Both payments are on their chains and locked to the same secret hash f4672cd9ebc9f3badf5a506cb73f09ed0f1efa09, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: cf0d099eefc7cd173f8ee0a0342fb60c77e7021c047b3bbb760f2b8817b40e1d
- TakerPaymentReceived: 27861c45e6d17689a1e47b292379603439a3132ba2a1a66fb3e32ad7fee9cce3
- TakerPaymentSpent: e3152263d3b0860ab1ff5f58dbea9942d88deecb3d2eded9a0f885fc6bf5834b
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 defistats-gleec.