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.
86faae7ee051939ca39f01b8dc8a1e3697b1bcb1e29729ca6dac0dc46ee78624
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 86faae7ee051939ca39f01b8dc8a1e3697b1bcb1e29729ca6dac0dc46ee78624
- MakerPaymentSpent: 584db4c1407b13fa49944cb9254f5469ba54fd736c677b552f0d3ee139cccb5a
8437190bf757a278ba16baae9e19ea4b57df3b2cb0aa45efd97b1a600b4cad95
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: 7bcdccea292facb42aebd73e2a23b17c4f049eaccb787f35c3305db712396f62
- TakerPaymentReceived · TakerPaymentSent: 8437190bf757a278ba16baae9e19ea4b57df3b2cb0aa45efd97b1a600b4cad95
- TakerPaymentSpent: f47564c0308145ba23b99bb64a8a988299e7fbec292868c76009d76ea15fadd8
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.