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.
525d172dabf38945ecad9d0f29d10c3378a63223bd04a549bf96769b121d3701
Both payments are on their chains and locked to the same secret hash 8a419a608eb2faecd759f58834fb523db146d585, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 525d172dabf38945ecad9d0f29d10c3378a63223bd04a549bf96769b121d3701
- MakerPaymentSpent: 9e390e939a2242b6166dafd56b2a3af2e4ad2acf87c17065ede136806409a1ff
cbc128b131e9346fd0c19ae90a04a39acb18fc8bdcc9666e2183d11e9d2a0628
Both payments are on their chains and locked to the same secret hash 8a419a608eb2faecd759f58834fb523db146d585, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b30e938c6105e5163df653ab55491246d7a762c77f72575ba547dfd43c87b499
- TakerPaymentSent · TakerPaymentReceived: cbc128b131e9346fd0c19ae90a04a39acb18fc8bdcc9666e2183d11e9d2a0628
- TakerPaymentSpent: b43a5b53be7d7a3236f28efdb3cf771f9edce3b0b96df242e6303dfae7cdb76d
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.