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.
5c3d0fa249e3636eedcea914850e7d457d37c9558b1cc0fc57d51e66185975ee
Both payments are on their chains and locked to the same secret hash 8e8da4ffda52fe09232961dd06f731cca36cdaf5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5c3d0fa249e3636eedcea914850e7d457d37c9558b1cc0fc57d51e66185975ee
- MakerPaymentSpent: f4a1065c6fb9ddd6a56cfe3d9511bfd865ee8012924722af0dd728ccd0f1b798
17fccaafefb9e01619f60638e8f427101dded26b98923ac735cc36887ee01b82
Both payments are on their chains and locked to the same secret hash 8e8da4ffda52fe09232961dd06f731cca36cdaf5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a8021f893d84718848de41cbfa413677a208bc140820e96df6238b47bce4bd29
- TakerPaymentSent · TakerPaymentReceived: 17fccaafefb9e01619f60638e8f427101dded26b98923ac735cc36887ee01b82
- TakerPaymentSpent: 78657ae1423681504b0273fdec7af1e01d64dfaa41d1d6997bf1b8403d8247bf
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.