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.
13e98b5f6acb8c8a02d142ac438343a421f6457c1545ebec6ff5bf04b8c75165
Both payments are on their chains and locked to the same secret hash d1f719396fa1dc887d2086d92b2f8721702490e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 13e98b5f6acb8c8a02d142ac438343a421f6457c1545ebec6ff5bf04b8c75165
- MakerPaymentSpent: f81f3407d8f7cf2276c654af5d525b388fb85bc56de490350bfbf0896f87a128
54e67a580cd18cd6f5f02ded4ff1792e6b064620852236175dab8a1a5d571f01
Both payments are on their chains and locked to the same secret hash d1f719396fa1dc887d2086d92b2f8721702490e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b748b123711946d3f06844a647727dc4e2b5953676effba01196a76f9f506ead
- TakerPaymentSent · TakerPaymentReceived: 54e67a580cd18cd6f5f02ded4ff1792e6b064620852236175dab8a1a5d571f01
- TakerPaymentSpent: 891a2ab287b2b1bd186781994b23dd043ef116de9646c8765543de677f6ede4b
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.