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.
bf4351b737edb46a15dd2fcb1f7a54b46048f4532900ea1fa36954715e5bab54
Both payments are on their chains and locked to the same secret hash c963ca4cfe82308d0297ac406f9de0ff6257060a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: bf4351b737edb46a15dd2fcb1f7a54b46048f4532900ea1fa36954715e5bab54
- MakerPaymentSpent: c35dd8f47259cb1de707ea777aed8fe1839d6761c9dab117171a0883298fdb40
03c835899b10cd6aa7ab6cfb7fad6f37b83fde277610d1dd90f4e40ac3ca2c01
Both payments are on their chains and locked to the same secret hash c963ca4cfe82308d0297ac406f9de0ff6257060a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e666d3547f63f14c2e35bf3443bee59b0522a6a01e740ec95c628efb35cbc501
- TakerPaymentSent · TakerPaymentReceived: 03c835899b10cd6aa7ab6cfb7fad6f37b83fde277610d1dd90f4e40ac3ca2c01
- TakerPaymentSpent: 0acdb36a0526502593faf0f12f17d3be127d1c610a72ddb5f16b2e979d1de118
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.