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.
294e6d902671762ded95da73ff093be77b278a5abe1cc697fa0f613eb9965954
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 294e6d902671762ded95da73ff093be77b278a5abe1cc697fa0f613eb9965954
- MakerPaymentSpent: 1270c7ee8c65222961a7e3f9afd2c3fc0a61c00729c7cbca5178c7d56d67b09b
9ac77bc91ffc2a8c190e502845b2613ffa5a8842b949ec4d77758ca693a119a9
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 71f870275cf44beacaee7fb72b1692e6a718964bc8df6b8c8956edf18c187995
- TakerPaymentReceived · TakerPaymentSent: 9ac77bc91ffc2a8c190e502845b2613ffa5a8842b949ec4d77758ca693a119a9
- TakerPaymentSpent: b3c3c4ab4ba9b8579c747a999cbb393c2b80f9d5395c4705c3ad52c9d7e2fbfd
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.