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.
178935d38368422807e402fbccfecf431ede2e74ac570dedccb0f9c52d6cf362
Both payments are on their chains and locked to the same secret hash 49691997c1ffe056f20cecba8355230b074049f2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 178935d38368422807e402fbccfecf431ede2e74ac570dedccb0f9c52d6cf362
965b704da55f9c510d44ff18402c53ae0e3582b468425475c339b4d7efe4abb6
Both payments are on their chains and locked to the same secret hash 49691997c1ffe056f20cecba8355230b074049f2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: bdc719a342fb625cee03d037d7fd22dd918ff0fdb788c71f1a3f41e1d4ae4bb6
- TakerPaymentReceived: 965b704da55f9c510d44ff18402c53ae0e3582b468425475c339b4d7efe4abb6
- TakerPaymentSpent: 7655d9920346e7a536d60ba57376e1b45b21e4d8eecb4dc196cb38afe95a9d45
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.