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.
1f5959841018389ed0e95ae16720abd57656dc578bb29b0c6941b5344b9d7c85
confirmed on-chain
- MakerPaymentReceived · MakerPaymentSent: 1f5959841018389ed0e95ae16720abd57656dc578bb29b0c6941b5344b9d7c85
- MakerPaymentSpent: 7a1a6393a54ea89724811764231ee240d9a06dbc322b33952dc6de8d277972d3
03c9c48886bd3df45b7466d8fa915cab4d749053067284b00115034cc9c5586a
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: 49fd47c7482ba08a003f3d70e2529a2bfb8d5a1be53867d40b4e0e28927031a7
- TakerPaymentSent · TakerPaymentReceived: 03c9c48886bd3df45b7466d8fa915cab4d749053067284b00115034cc9c5586a
- TakerPaymentSpent: cd3cd7b54b305d57872520713cfd452452f00ff7231b44b5ac49aca1406f2402
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.