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.
7868c934a68ab62e584f4fd5daecd8299e4e0ce6de7e5ecb8807878bb71682f4
Both payments are on their chains and locked to the same secret hash abb885bc7b7f937a8c8f9bcc0c46e7da7d1d2a82, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7868c934a68ab62e584f4fd5daecd8299e4e0ce6de7e5ecb8807878bb71682f4
- MakerPaymentSpent: 842648386637b11eeefb753b1f752927de6207ae41b5b238ee586dcd27d70dc4
551d566bf1827cc897918c26147185473cb5dec0fea58c56b9a08a001db581a3
Both payments are on their chains and locked to the same secret hash abb885bc7b7f937a8c8f9bcc0c46e7da7d1d2a82, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e0c2ea8c4b70a2bdbb4eabf7ffedaf21f55f9149a8f2147db397c45a990c8081
- TakerPaymentSent · TakerPaymentReceived: 551d566bf1827cc897918c26147185473cb5dec0fea58c56b9a08a001db581a3
- TakerPaymentSpent: e1a37fb197eefc903cf7116f2d534975f4b88e5d634d08b56d3579b97e81d58f
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.