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.
13d37958b441c834c7690efdb19829967f338998ac945654f5a9961de78364d1
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 13d37958b441c834c7690efdb19829967f338998ac945654f5a9961de78364d1
- MakerPaymentSpent: fb1975d886f5d448666e67eddede5c0fb67b385bd658cdbeef13b4f206d6b588
350721b4a461e2eb1cea573918cc2806fe25e906f944723251b72ccdb45fc1e3
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 93f28c3827d596de8e8a46474853df315f2d27f123826b0b31f69e775a715a3d
- TakerPaymentSent · TakerPaymentReceived: 350721b4a461e2eb1cea573918cc2806fe25e906f944723251b72ccdb45fc1e3
- TakerPaymentSpent: f306f40fd74c1350aa2ef1ad645d86bd0518455a88af11f03866c902e88cf581
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.