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.
8866c578344b7ea94a1ddf952c1826665a10ac2e4bcaed28bb7b539adb796788
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 8866c578344b7ea94a1ddf952c1826665a10ac2e4bcaed28bb7b539adb796788
- MakerPaymentSpent: 0994161e6a9ff9d5f6ee53113d4e094b1b7f6bd0497b381eb1787279dd17ec04
5cfb7c2b9133110461d05ecc2e31f59e1e527d63cca8c12515400b6302c74aa0
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 28effb0169a2b6d8b6fd4a1a5f72dd623805d1725c2e717956d18d03cea9e554
- TakerPaymentSent · TakerPaymentReceived: 5cfb7c2b9133110461d05ecc2e31f59e1e527d63cca8c12515400b6302c74aa0
- TakerPaymentSpent: d2be24be2ce5c84e7ae0695323a6e3d6a704d75eaa12f809586f6f3ccb4e229c
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.