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.
035fda04bd250383f3b24dd000c76d156cced66564b473da79401fd39df98cee
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 035fda04bd250383f3b24dd000c76d156cced66564b473da79401fd39df98cee
- MakerPaymentSpent: 0de901344d6fb848f9fd73eb8dd03745f3d9a3d0e5d9341d0a089708c41d33ee
5901543f17c0f28fb4090aad208fbddd5ab6786f449dcf799d5866248d8e9c9b
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 3d278e4a16bf26f750d64dfeb3db33c66b197b7c40bb23ed5dfa8968fda531bf
- TakerPaymentReceived · TakerPaymentSent: 5901543f17c0f28fb4090aad208fbddd5ab6786f449dcf799d5866248d8e9c9b
- TakerPaymentSpent: 8aa12f89842eb44608107b9d76bc003a0b5595b4db62b69e4ac80fc179b578b1
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.