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.
fde07c7f97995b230613746d4bf4599e6c4dc69f5e58897411b6725716f2f98d
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: fde07c7f97995b230613746d4bf4599e6c4dc69f5e58897411b6725716f2f98d
- MakerPaymentSpent: e0f1e30fc6170267fa0986498730864ede209201f900ff652fa86b5fa38529f6
0d0fc4094a9e495e10a494b3a732b7b0e21d71c64547b79caf7727fbd834692d
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 55b898990d16351e9a3094107fd1d3712f7dcd170347c30ece8b61db2ef5de7f
- TakerPaymentSent · TakerPaymentReceived: 0d0fc4094a9e495e10a494b3a732b7b0e21d71c64547b79caf7727fbd834692d
- TakerPaymentSpent: 44011f574b48691c9a596fb1b92db65322688cf136f7326b1fe2fa5d679c8e22
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.