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.
8697894488998784b7bd15caa3ef510e3d13acd956eee3690f1ff2fb4a852780
Both payments are on their chains and locked to the same secret hash a45108dd5eb1ae5b206e7573bbdf0fa3dc22a7f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8697894488998784b7bd15caa3ef510e3d13acd956eee3690f1ff2fb4a852780
- MakerPaymentSpent: 003143872e9a8c4fd27e1275b7c6c7c858a98237fe0e5de2826464aa0b3bcc8d
665bf8f42cb0e281f115e45f023885fc27e188d056f57ccd20c2dd5102d9cf8f
Both payments are on their chains and locked to the same secret hash a45108dd5eb1ae5b206e7573bbdf0fa3dc22a7f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 594ba0f32c4aea415d5df1be349172d9c8f4e07d1f987ec632ce62f8d35ceb1f
- TakerPaymentSent · TakerPaymentReceived: 665bf8f42cb0e281f115e45f023885fc27e188d056f57ccd20c2dd5102d9cf8f
- TakerPaymentSpent: a1f60afffbd8846e25098bbcff1bc59aab996e5cd0a655e1398de8bd75b14f0c
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.