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.
92c5f624ac14212faec3fc43f1ed61c2c9d4359b0d2078428c95b9597ed886f5
Both payments are on their chains and locked to the same secret hash 565acab4fd7a7862f9c040fe554d3d264cb72c9e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 92c5f624ac14212faec3fc43f1ed61c2c9d4359b0d2078428c95b9597ed886f5
- MakerPaymentSpent: d69e8133f0cbf51dbce32eec4298dcd977eadc3c92e76c0f8b4d14c41818f076
bd232e5759a82866487ae8f0869d3548afd5e0c47ab4a12ff5e6ed6eb6a52237
Both payments are on their chains and locked to the same secret hash 565acab4fd7a7862f9c040fe554d3d264cb72c9e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d31e9fedeb630f142fb0d739e11508d8d2fe280ff428142c931b90cdd80c2afd
- TakerPaymentSent · TakerPaymentReceived: bd232e5759a82866487ae8f0869d3548afd5e0c47ab4a12ff5e6ed6eb6a52237
- TakerPaymentSpent: 005e7c0d8a6c7d8cc2ae96cc76c5af3a9e58c16f4b938beed45955a32f88f71b
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.