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.
56139877e5bc00641a03ec5cfa40db753447408e2504ab0315e9ec41627fff07
Both payments are on their chains and locked to the same secret hash cee34e00cc4ebc944515dcab914d447d6ccd0ad9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 56139877e5bc00641a03ec5cfa40db753447408e2504ab0315e9ec41627fff07
- MakerPaymentSpent: 8d75349f473ef8fe0bf2aee53255d404c655473903958e346d80bd38ba2fbfb0
0edd29eb666e24533f7a49db0c7219b91fa344ebef1bafb23791222c14376d1a
Both payments are on their chains and locked to the same secret hash cee34e00cc4ebc944515dcab914d447d6ccd0ad9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 61fe378eb2baa55c54a36ddad4c54cc7453514385860cdcf0bbfa2ffc60e9a6a
- TakerPaymentSent · TakerPaymentReceived: 0edd29eb666e24533f7a49db0c7219b91fa344ebef1bafb23791222c14376d1a
- TakerPaymentSpent: 9cfa384a8b69283f81826952812ed70ea6fd53ea25817e15d6bce9ca4c1188cf
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.