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.
177a8ea394dcb6c9f316307f7c1a071a152c9ed6d39b06386db3fec1ff422cd8
Both payments are on their chains and locked to the same secret hash 496a6baa2d24dd449b5b5a7cddeb6c916d5906f7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 177a8ea394dcb6c9f316307f7c1a071a152c9ed6d39b06386db3fec1ff422cd8
- MakerPaymentSpent: 662a780640082a1c473c86d5fdaf205bfa617a94dfe25bcde2a0981e9a20af71
046ab392e548b2fd0cd0fbcbb4a37df28a6ece9f194416c6e91f894eb33134ea
Both payments are on their chains and locked to the same secret hash 496a6baa2d24dd449b5b5a7cddeb6c916d5906f7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a2ce82dfc654c35cf51c427e1147c9d1805155e43997f175f6a2a7e62afde335
- TakerPaymentSent · TakerPaymentReceived: 046ab392e548b2fd0cd0fbcbb4a37df28a6ece9f194416c6e91f894eb33134ea
- TakerPaymentSpent: 855fcfcc86a487ec6c4b7df0dbe4a4b499d49b36a2ddd17d802d1ef70d163776
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.