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.
e878a9910ff79432db5fa2419997451104109b1e58f5dd2acdfb262d667a38ac
Both payments are on their chains and locked to the same secret hash 639238770aed588058bb96f4ab0135c3c8efcfbb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e878a9910ff79432db5fa2419997451104109b1e58f5dd2acdfb262d667a38ac
- MakerPaymentSpent: 468bc61972dfb634880c0e3c67821f9ae363bf40e3aafb36232d59a8e62747a5
8e3d2c302eb2121c3d4afc9747bf0f55f0bbb06fe526774eeac03488b132e8a9
Both payments are on their chains and locked to the same secret hash 639238770aed588058bb96f4ab0135c3c8efcfbb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a3cf25c80822bebcafe0e3c778d84e73e22683e0f2448b817c7cbf331b9be9d4
- TakerPaymentSent · TakerPaymentReceived: 8e3d2c302eb2121c3d4afc9747bf0f55f0bbb06fe526774eeac03488b132e8a9
- TakerPaymentSpent: 27add691df8aff2f8be680b3897bcc387f243c8acf51d4938d119da157d14e10
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.