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.
b8fbf7617b3e635fa10ffcf9a62879389f3d35f0b13b4405f3cf526fa93672e7
Both payments are on their chains and locked to the same secret hash 7eac3a04c5a44ab70824cbc966d4dc487865810d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b8fbf7617b3e635fa10ffcf9a62879389f3d35f0b13b4405f3cf526fa93672e7
- MakerPaymentSpent: 16e1b554b685e173a55477e301af6215f3d0c6993cbac460181ef42b783e6778
414d71774696c644ceae02b918ff4b39bbca325cf09e78049514e48ebc6525cc
Both payments are on their chains and locked to the same secret hash 7eac3a04c5a44ab70824cbc966d4dc487865810d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 028f673f909b1e9f2340699930a41eb9740d5bb47b4faecbebfff5fdcd48a0b6
- TakerPaymentSent · TakerPaymentReceived: 414d71774696c644ceae02b918ff4b39bbca325cf09e78049514e48ebc6525cc
- TakerPaymentSpent: bf4c0d80601d16e26849d8a558534fb80934b2c395b51ed6ac24183fded6337c
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.