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.
dff77d20779d925ea17c049d29dd6b3cef78f2f6060d4e9f11bf0a91b8f2877e
ARRR settles as ZHTLC, 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
- MakerPaymentSent · MakerPaymentReceived: dff77d20779d925ea17c049d29dd6b3cef78f2f6060d4e9f11bf0a91b8f2877e
- MakerPaymentSpent: a2bbaf1031377729141ac4a079be32cf3b32adaeda29a78ec8b8a4b03b094ace
757d4681c49e0a61ce17c290d2276c4ff14a953b162137a37e246c45d79daa01
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 001fb4249e3e0cc176928827ea67e28f10bab72f90c8e2b309e1607e98b36a50
- TakerPaymentSent · TakerPaymentReceived: 757d4681c49e0a61ce17c290d2276c4ff14a953b162137a37e246c45d79daa01
- TakerPaymentSpent: 55aecf20ab07f9097bb89203f9d9e90c296624f42d7bfa997126c89c81890324
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.