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.
27d1296747e1f1b17c279e7ca7dd7547be60cff4ac6eaa6b7b9b74ded6b42693
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 27d1296747e1f1b17c279e7ca7dd7547be60cff4ac6eaa6b7b9b74ded6b42693
- MakerPaymentSpent: b9a976ec823eafbb2fe5f0b2d49ab9e92f997cd839b275c43dbb4830587d76d8
32c5bb0b9ed7ce7b11043ba817fe2afab9c0f90b67129e9017935668d94829e7
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 254da5ee376941aa95914d09a3ce7a62c7423896c3c33ab218a6514ca04701a7
- TakerPaymentReceived · TakerPaymentSent: 32c5bb0b9ed7ce7b11043ba817fe2afab9c0f90b67129e9017935668d94829e7
- TakerPaymentSpent: aa6d761de947ffc0ae99480899e375839d5aad50eacf4de4f2cd2eaa07636c2d
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.