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.
18ffe80f285ea0249c1a69d50cea576be8f9b1df6fe21b4bd5efd3241aa8ea5a
Both payments are on their chains and locked to the same secret hash 7cf436da10e25a50bb622c99912241849c5dae31, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 18ffe80f285ea0249c1a69d50cea576be8f9b1df6fe21b4bd5efd3241aa8ea5a
- MakerPaymentSpent: fc0276aae39e91373c71105fbd3ae0fcd0e4eec478b6174262c470d80f3e2d37
682a3dec21e25f07a3725bdc8aabcd7082eae64161c25b91a6d461e1cb7a2e8c
Both payments are on their chains and locked to the same secret hash 7cf436da10e25a50bb622c99912241849c5dae31, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 76602eff70867adf8df7c84a9c6482d30bd2a97c2baec68e0ddfbc64bb4a87e7
- TakerPaymentSent · TakerPaymentReceived: 682a3dec21e25f07a3725bdc8aabcd7082eae64161c25b91a6d461e1cb7a2e8c
- TakerPaymentSpent: a65f5e4fce25ea1c1fae2e8d8df2f7b0e8501b13897fa7922ed8495b8ce11794
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.