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.
bb320775767c8b7abea1dd20a76a8ca33f2a16c5dae5f8cce9b0b9d04dbc1296
Both payments are on their chains and locked to the same secret hash d16ef16f390d9a93bf7eadf41d3e5d65a942df7f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bb320775767c8b7abea1dd20a76a8ca33f2a16c5dae5f8cce9b0b9d04dbc1296
- MakerPaymentSpent: b49a7b1e5aa002ec0b7263791465c3b64851102b1e7d12b3882d8872813f5010
433c6fd8c81b763b6623929169aa3f138841460dc80d0b83ca485d4667779b25
Both payments are on their chains and locked to the same secret hash d16ef16f390d9a93bf7eadf41d3e5d65a942df7f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c1cb5db0a0587a1cbaa3c9c0f811e0a9e6dbe071af21de92c50e03d49b648c2c
- TakerPaymentSent · TakerPaymentReceived: 433c6fd8c81b763b6623929169aa3f138841460dc80d0b83ca485d4667779b25
- TakerPaymentSpent: fd3545f2203d124fb2553c63299cb1cd18afa71c968674a25c21262016d5bd79
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.