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.
d4ab2ca93d19ec36984e61ae93bce10287a6be9ffabba1a65091a87e2e06fa39
Both payments are on their chains and locked to the same secret hash 2bcb9cad0f2cc2221824845edb63965de0852a69, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: d4ab2ca93d19ec36984e61ae93bce10287a6be9ffabba1a65091a87e2e06fa39
- MakerPaymentSpent: fb2219e17ec4811bd4f032d193fb9e3d7a2d2d94fdbd4bc1392e751baace0296
44e0eb7561b7a45b894c1013045836c97cdf853048a0a93c9a955ec9531769e0
Both payments are on their chains and locked to the same secret hash 2bcb9cad0f2cc2221824845edb63965de0852a69, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2661e7fcdecb2e0790eeb78d42bf373327a6a9725d17851935d8f515aeeed710
- TakerPaymentSent · TakerPaymentReceived: 44e0eb7561b7a45b894c1013045836c97cdf853048a0a93c9a955ec9531769e0
- TakerPaymentSpent: e26ca22b0c551c54763f8cb830f2926c6c233ba1dd26a18d3627aa89aebf0ced
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.