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.
039fc524b59e05d2c88be2274531915eba4faa5dc4aeb98f16df2a87f3e0c721
Both payments are on their chains and locked to the same secret hash ff74cd2c217bbccf8f0a182aa142cb1c7272f580, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 039fc524b59e05d2c88be2274531915eba4faa5dc4aeb98f16df2a87f3e0c721
- MakerPaymentSpent: 7d9535772e8d3c1ee8c63d40679dbc38f66be929c4ce9628e41dadf4cd380149
38a3ad5925bfe7b2e6328f03d751f1fb8801c388d975631b77dbbe2400b05443
Both payments are on their chains and locked to the same secret hash ff74cd2c217bbccf8f0a182aa142cb1c7272f580, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6a0dd1d0aa4d5736126bac320ac8c6691d1b65a061eadb035838840793899352
- TakerPaymentSent · TakerPaymentReceived: 38a3ad5925bfe7b2e6328f03d751f1fb8801c388d975631b77dbbe2400b05443
- TakerPaymentSpent: 02a49ce0722b7383ad7ab8780988a604149b3fe6ded8e4f3bb8e3f7585050c2d
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.