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.
3deb817ec32f4b067c2f06cc679b5408ae62b710cfddef407bb51fd3646776ff
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 3deb817ec32f4b067c2f06cc679b5408ae62b710cfddef407bb51fd3646776ff
- MakerPaymentSpent: 5812d00e1f4253fa361f952988c9156747197de6451884c522ba00e6e8a21ac8
920e1d1149162da5306f8f6b594955c3f2325d85482188968c55254bfded3c4f
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: e46b5c80ce9133d859d4b4d913e00e6fb5dccd1afdbab872da3ce6a2a65e40af
- TakerPaymentSent · TakerPaymentReceived: 920e1d1149162da5306f8f6b594955c3f2325d85482188968c55254bfded3c4f
- TakerPaymentSpent: 9d50fcc274181912e26b8d615be9acf825d8ef14bbfd60b38d7383e659c44998
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.