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.
f3726986572aa6f51f78aa42094fa06e22c1d1f5fdbab7caa3eb06fc5d940945
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: f3726986572aa6f51f78aa42094fa06e22c1d1f5fdbab7caa3eb06fc5d940945
- MakerPaymentSpent: 5ca8dfa6e07e12b547edf06ab5144b3dfa8e4ce2024f3eb86fd6e0632fa08147
ab0a19c558e2a3ed6730e78ed9ced6374ccb35fd5d23a78418fa7ba01996a60a
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: 1fdb548c62b89fea2959b7ff9497849386ec958d6a4284cc2526c0d15f5cfa87
- TakerPaymentReceived · TakerPaymentSent: ab0a19c558e2a3ed6730e78ed9ced6374ccb35fd5d23a78418fa7ba01996a60a
- TakerPaymentSpent: 4598e396c3a4065f06bdd3de4210706507987155b3bea1a988d78fd78cc3cda8
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.