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.
3f28ec844c511ce8db1837710cca7479349534ab5aa327ac1007b9398cda2646
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: 3f28ec844c511ce8db1837710cca7479349534ab5aa327ac1007b9398cda2646
- MakerPaymentSpent: 39220f189131d8b3b9ded500a0f67822ae6ea1328603c1f792c119b61abd101d
4bd53e6c6dfd10c5b643c95538fe3c7a99b8721fc702d71a2950ae2c20c49c4b
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 942f7687f821308267eea10e378ffaec2a3e98ca3476df08f02f5f64b8e6e522
- TakerPaymentSent · TakerPaymentReceived: 4bd53e6c6dfd10c5b643c95538fe3c7a99b8721fc702d71a2950ae2c20c49c4b
- TakerPaymentSpent: d6e8496b8776903201804e13ffee6c792449f39d039a966483e0f6548b52715e
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.