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.
278afda5b3f0e3a782d2f605cffc44523c5fd29fd64d81bbf4c272d50c48ff18
Both payments are on their chains and locked to the same secret hash 676064f634d82db87a0d0c2dd6fb8701d3fcf895, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 278afda5b3f0e3a782d2f605cffc44523c5fd29fd64d81bbf4c272d50c48ff18
9b4f1466b365bfd46638617101f27fa060253f18835600bf7507b939ebdddb05
Both payments are on their chains and locked to the same secret hash 676064f634d82db87a0d0c2dd6fb8701d3fcf895, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 90aaada426462f870911728b9618344d58e5b3d264453d6055f38c00b1eac216
- TakerPaymentReceived: 9b4f1466b365bfd46638617101f27fa060253f18835600bf7507b939ebdddb05
- TakerPaymentSpent: 0721b6a47ae8623f951e5549d72a370508810acca849caf39c68010adec4eeeb
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.