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.
688316e4a9b56e6211f9e0ac6be698faed20f6e05c5a0c160e2a5487be227646
Both payments are on their chains and locked to the same secret hash 061a95da255df602900838af7e854cbf05b6168d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 688316e4a9b56e6211f9e0ac6be698faed20f6e05c5a0c160e2a5487be227646
fcf3d3bcae94f7a94e6e93dc1d41e5ce011951ae6bd115bba171201e765a7068
Both payments are on their chains and locked to the same secret hash 061a95da255df602900838af7e854cbf05b6168d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 91485c633913dca9af5b4ff78e28dd16c8356669843284c921a1912ec493c32e
- TakerPaymentReceived: fcf3d3bcae94f7a94e6e93dc1d41e5ce011951ae6bd115bba171201e765a7068
- TakerPaymentSpent: 4c3667d685a6ca5e6de5e841f10403db905361a753a8319fdced65be1bd19242
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.