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.
817b9645ebf38ec7aa5fe491d26f249e97aa2be55b531368e14c920c68b1068f
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: 817b9645ebf38ec7aa5fe491d26f249e97aa2be55b531368e14c920c68b1068f
- MakerPaymentSpent: a03ab2e9c722225ce62d52ce9838f50520164201b1e6d7c21eedea5a4a312fcf
2988e258c7e019c17ebe038111a8c1d6844730c723d44a6b3e7fdfe78a855345
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 82f799cc10bcfe2dd95f3dbd9914c39ad4dc0c110c677d9bf90b63796b2ea29c
- TakerPaymentSent · TakerPaymentReceived: 2988e258c7e019c17ebe038111a8c1d6844730c723d44a6b3e7fdfe78a855345
- TakerPaymentSpent: e26471a68c934c886f1976c804ae9551ef353dd900a26ac76b0a5daf9b97c868
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.