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.
dca1c97e76e949b4c5887dde745a65863fe51985090173ef49acbf69a13002dc
Both payments are on their chains and locked to the same secret hash 53084ecafb3c054192ea0a2e85549f28a5f14e22, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: dca1c97e76e949b4c5887dde745a65863fe51985090173ef49acbf69a13002dc
369542a5ffbe93311c09f6c31f7d342578d556d6aa9490f0e17445a51f802672
Both payments are on their chains and locked to the same secret hash 53084ecafb3c054192ea0a2e85549f28a5f14e22, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 639a77511eb1968a97fa6ab479447b76002390fce751dfa7619fbcce784c30b3
- TakerPaymentReceived: 369542a5ffbe93311c09f6c31f7d342578d556d6aa9490f0e17445a51f802672
- TakerPaymentSpent: 80d2faf06d4b3f09ec4204f607faf5f8589113e23981e888e1daec016ec57901
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.