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.
83564027a4a0fe9c3ea5798c22573f736dc4eb1645287630d6adf21ec38d54d9
Both payments are on their chains and locked to the same secret hash abb2e5c8924ad4aa05eae528a8db239c4830a674, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 83564027a4a0fe9c3ea5798c22573f736dc4eb1645287630d6adf21ec38d54d9
- MakerPaymentSpent: 54607f38d38d4d7cae554f5e8e00f0276b2b108e72b70d6676668c151727807e
d5a8e15ce5777a56dc7ab3ce688c2e735a962cede0d553887e7e5d798cc60a36
Both payments are on their chains and locked to the same secret hash abb2e5c8924ad4aa05eae528a8db239c4830a674, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f99bd3006263d61a121005a7f73382a2d5bca44208d64824d965cf7aea2dd719
- TakerPaymentSent · TakerPaymentReceived: d5a8e15ce5777a56dc7ab3ce688c2e735a962cede0d553887e7e5d798cc60a36
- TakerPaymentSpent: 9182c1d1c8a84476a5912643135ab4e61cd3dc8e43d1862c329e65d81df1d3ae
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.