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.
4dfed43000d40eb38ad012719383f64977d4fc4f9732c357bc38e768dc877f43
Both payments are on their chains and locked to the same secret hash 5af6a0b5f1f3c9cb5f6b8ea7355935cd2cd6be2b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4dfed43000d40eb38ad012719383f64977d4fc4f9732c357bc38e768dc877f43
- MakerPaymentSpent: 69fa2052a39a453598833a6587e4094338313f1176d83717c8bcaad66ec31d30
5a1a36af28282864e97e011892f26d54174e62765210a57aad0111b3304029a5
Both payments are on their chains and locked to the same secret hash 5af6a0b5f1f3c9cb5f6b8ea7355935cd2cd6be2b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 02adfc3059e7732d388fd40de2b072849bd49340bdb825ae741bd0ef86f27ee9
- TakerPaymentSent · TakerPaymentReceived: 5a1a36af28282864e97e011892f26d54174e62765210a57aad0111b3304029a5
- TakerPaymentSpent: 6af645505d84ef9fa35c0a0942e9880791c2049cc7a49b57684f611953205958
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.