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.
3f342cb569e590878a3c95ca09159216ce56239eea7d6f44abb5799d3d7a5c5b
Both payments are on their chains and locked to the same secret hash bc16d761e2b4b5ec7c89a89a4e26631d487de229, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3f342cb569e590878a3c95ca09159216ce56239eea7d6f44abb5799d3d7a5c5b
- MakerPaymentSpent: 0cee72d318f2f21273957f1678e27665242118469482a9e1be21b57da03e1d5b
2230329249b4a47a7cabd89c2f9fd7469eb840c8e5f2a13c703abc5683c6769e
Both payments are on their chains and locked to the same secret hash bc16d761e2b4b5ec7c89a89a4e26631d487de229, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 87458da4cd222e4d5699ac373aaba1cb9fb4c03f5d886e8abb182218a24bee14
- TakerPaymentSent · TakerPaymentReceived: 2230329249b4a47a7cabd89c2f9fd7469eb840c8e5f2a13c703abc5683c6769e
- TakerPaymentSpent: 12b70a29f8ccd8695727b7becab275781e641acfbd8edd762493b02daf4dbf0e
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.