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.
b401cf208001f08c57439faf66079ee5027b9a7d5865e38c86096a5a1dd21000
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
- MakerPaymentSent · MakerPaymentReceived: b401cf208001f08c57439faf66079ee5027b9a7d5865e38c86096a5a1dd21000
- MakerPaymentSpent: 70bb434c9a6022646f580fb7f981ee209e2f4857a8392443b4ec187d18bd52e1
57a108d2a50c34bdee7a86ecff78e8134055e1b77b69acfab534eb086b23986a
confirmed on-chain, calling the swap contract
- TakerFeeSent · TakerFeeValidated: 79556263377d7892b03274415cc1a5f3672c502603e22ea71e065794af3e93b2
- TakerPaymentSent · TakerPaymentReceived: 57a108d2a50c34bdee7a86ecff78e8134055e1b77b69acfab534eb086b23986a
- TakerPaymentSpent: 2b3713b6c90b6bbe8a579a43606f64b6c69ac474cc25d27d30af350691b9b217
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.