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.
8ac81f65abcf8a27eeeba486cf69069a305c98eb72b2afe9d6a6862dca7f442e
Both payments are on their chains and locked to the same secret hash 8c9240f9739039388bddea631865aea9350a00ba, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8ac81f65abcf8a27eeeba486cf69069a305c98eb72b2afe9d6a6862dca7f442e
- MakerPaymentSpent: 0b9531077cb56ab74b1e7cde0bf36ed0bc8214990067ef273e3319ed6c606170
ed326034cec3ab4e939aaa2fc98f058c69f0c6c60a9878192edc97834a9e7969
Both payments are on their chains and locked to the same secret hash 8c9240f9739039388bddea631865aea9350a00ba, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 43051276cf2078212d2226605130949f9f973c39f44fbf3d6b9fc819782eea19
- TakerPaymentSent · TakerPaymentReceived: ed326034cec3ab4e939aaa2fc98f058c69f0c6c60a9878192edc97834a9e7969
- TakerPaymentSpent: 00407bf11bc0cee5c108efec39c9282cd102b94a354bfe9c33b47282f80c4ffe
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.