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.
330dfd3f732d627208ed4c1e7cdca15e345b50158d2ebde3e396a248100ab70c
Both payments are on their chains and locked to the same secret hash 66f7db399d4c8c50f5e2934eede89386e0eed97b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 330dfd3f732d627208ed4c1e7cdca15e345b50158d2ebde3e396a248100ab70c
- MakerPaymentSpent: 223161d54d5dc704e3dcb61de832dd40c9af84799ede046005e090411da76066
e4635f273fe00ae0d0278647726236900177cfdde6e63d038317f5534a43f797
Both payments are on their chains and locked to the same secret hash 66f7db399d4c8c50f5e2934eede89386e0eed97b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 929862beeb2b818fd7cd9d8c77659ce2b711cf7072649c10aecb15f2f7a71f45
- TakerPaymentReceived · TakerPaymentSent: e4635f273fe00ae0d0278647726236900177cfdde6e63d038317f5534a43f797
- TakerPaymentSpent: 17d489c21afa0b03c3b0b3071765d5adb980dd0d4d394f6634313b749b42db17
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.