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.
ac067e21153a802658ce1eba1150d1c90ac00fab1f2862ffaaa1a1fc6390c8e5
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: ac067e21153a802658ce1eba1150d1c90ac00fab1f2862ffaaa1a1fc6390c8e5
- MakerPaymentSpent: 31aee2b8e678c214c06eeb8065ede7640e3bd61865e8cfc5c4f2a41c921e803b
7bc355340c36290b2adc8b1076cf1d71a43d3faa63f5e4e1353b748917738d06
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 775dce485e433e0e82262a510ff43c175c06febdf2a5f22aeb1b4243ea21de13
- TakerPaymentSent · TakerPaymentReceived: 7bc355340c36290b2adc8b1076cf1d71a43d3faa63f5e4e1353b748917738d06
- TakerPaymentSpent: f7555f541ffc66be4b82292235c34495c3dcfda2a5a5a0e013bfe0ab0198e7b9
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.