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.
9c4418e65717872d2d429cbcaf8c2782bf502afe1fa404d7ac73ffd5cf06fa6c
Both payments are on their chains and locked to the same secret hash accdfa86e66037778326a4b75cbe5feca9a97360, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9c4418e65717872d2d429cbcaf8c2782bf502afe1fa404d7ac73ffd5cf06fa6c
- MakerPaymentSpent: c090f01d3f9f5aabab49d4d98c38b6e0eacfc223755337273a65bb5d1b04c052
30d196e08f7459232940b1b26bfe0160164ffd5773feee954810b22ec77a8108
Both payments are on their chains and locked to the same secret hash accdfa86e66037778326a4b75cbe5feca9a97360, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fec623de6471fb4f854c63b5557500c0ce34ce4aad16a6388e718c2e5e5c570a
- TakerPaymentSent · TakerPaymentReceived: 30d196e08f7459232940b1b26bfe0160164ffd5773feee954810b22ec77a8108
- TakerPaymentSpent: 25443431e8ca70d4bff1647049256b7e61e008449a62c28867a33df1f5255cf8
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 kdf-statsdb-8762.