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.
e556b0039dcdadd6d166749bc8a1db3a961dd6598553c1847c0681ab78f7ea1c
confirmed on-chain
- MakerPaymentSent · MakerPaymentReceived: e556b0039dcdadd6d166749bc8a1db3a961dd6598553c1847c0681ab78f7ea1c
- MakerPaymentSpent: 61d5430a0063a8a3f9585d73f110354b0c6d67436235683a4d93adfbf48ed2cd
49793144a50d3feb9e339ef9683c67308ed804a77a6b11288232b1384b8089d7
SC settles as SIA, whose transfers do not appear as an output any chain server can read, so the transaction the record names cannot be checked against a chain here
- TakerFeeSent · TakerFeeValidated: c69d5943dfe3d271a4731778009decbe866684097c80fba010adc82b64578e1d
- TakerPaymentSent · TakerPaymentReceived: 49793144a50d3feb9e339ef9683c67308ed804a77a6b11288232b1384b8089d7
- TakerPaymentSpent: 14d5aa34948914b74af7e7dd486ae6dfd8b923fe280d5bb4b31d3bb086b53322
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.