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.
0382e48de03778d30e29d94d150d1f6ee4df0b2365f1af3060e4f99e6ea4f2ca
confirmed on-chain
- MakerPaymentSent · MakerPaymentReceived: 0382e48de03778d30e29d94d150d1f6ee4df0b2365f1af3060e4f99e6ea4f2ca
- MakerPaymentSpent: 5f7e7dc7eaba5b3cfadd765e987e53fd51c1f07766b37c5087b5a5a8cccf6f11
6c8dd76e7d8d30661c5c2743cc2f537c8eb307a026119fbc2a0f1344051a4cf0
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: 699bdc961974b9a8243a9b2b56ed2aee25149a234749022d63e6195e79dee77e
- TakerPaymentSent · TakerPaymentReceived: 6c8dd76e7d8d30661c5c2743cc2f537c8eb307a026119fbc2a0f1344051a4cf0
- TakerPaymentSpent: c499877f0edc6c6de83854c0a4146f0310ef53d06cafedc4a3ba5d0e6474a4ac
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.