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.
892b44561576e0a1ab7bf24b6cadb91a26cd755a7165929a459c2730940eaaf6
Both payments are on their chains and locked to the same secret hash d8931473541df96a295d47ecbaf4a8abb1f38f41, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 892b44561576e0a1ab7bf24b6cadb91a26cd755a7165929a459c2730940eaaf6
- MakerPaymentSpent: 72b439f042e9630a364d2b2cbdf6f069272345f700e8f0e8abd49c38107116a9
c8c0fab1b26d33a3014c2b3be840440d7ae82bdb0f1584d38ffdcdbb3d313cf7
Both payments are on their chains and locked to the same secret hash d8931473541df96a295d47ecbaf4a8abb1f38f41, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: eff23341971cc577b45cd80bf1530a3f73c3126c4b11f13d5b6f515709cf8c7e
- TakerPaymentSent · TakerPaymentReceived: c8c0fab1b26d33a3014c2b3be840440d7ae82bdb0f1584d38ffdcdbb3d313cf7
- TakerPaymentSpent: e4838bc1c4b7a40d7747bb02498a45a0b0f3fe7aeee4c39658ba958d1a3d79ef
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.