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.
0d92397b267dddcfac24cb05ad51e8085d23ddbd1b5501ce1420bb8f2c12e304
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 0d92397b267dddcfac24cb05ad51e8085d23ddbd1b5501ce1420bb8f2c12e304
- MakerPaymentSpent: 9fdbbaf12330100c8607ed19b8829c8a93cd64cdb34f3e2f2e5d5bdce0b6b968
99a7267ce33edc42443f989111509b470d3bf11dc49dfc15efd184662f0a7c9a
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 37855633322d32c43fd26347c108a111e14dc99510eee44a0a64ac547fe86b96
- TakerPaymentSent · TakerPaymentReceived: 99a7267ce33edc42443f989111509b470d3bf11dc49dfc15efd184662f0a7c9a
- TakerPaymentSpent: b872c3e1e55e90027391ab94a5fe9b9b6d78fdc79f982e80fef1a95c3272a644
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.