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.
813f77cb175a0b1f4c6d9ceed6e9216d8144dc917473fc15e6f3972b15ade9ce
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: 813f77cb175a0b1f4c6d9ceed6e9216d8144dc917473fc15e6f3972b15ade9ce
- MakerPaymentSpent: 9728e174853e370254cc1146f548737da1a1d7dbd2d3bb22a9243785d9df8476
03518131b430cefebc0d0a71bc38640de996c15b27114fe4c6b275425ae6f8e7
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: b0805063907c104479d6a22604ceca35a419b80131c04698f53bab48d499c024
- TakerPaymentSent · TakerPaymentReceived: 03518131b430cefebc0d0a71bc38640de996c15b27114fe4c6b275425ae6f8e7
- TakerPaymentSpent: a957304184bf505169574c4ebd54f0f62e68507cef7de46be2b178a8410ab5dd
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.