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.
d7d6765eb35f97f730a829933ff72f38463e248d3949dcb45e458cfb88cbf46a
Both payments are on their chains and locked to the same secret hash 74f549451f3366d566b052835469a7f8050c466e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d7d6765eb35f97f730a829933ff72f38463e248d3949dcb45e458cfb88cbf46a
- MakerPaymentSpent: a4712e1718eab1030072324bb71029598d21892d375966b464b8bc74f792923b
d6efb5df6b5b01f874d9a6210d64be327b980a9354cd06c629687b4e577a16fa
Both payments are on their chains and locked to the same secret hash 74f549451f3366d566b052835469a7f8050c466e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 23f2e861e4e987b23f4db8761ef28944e066cd97533e10887648432b02170c8a
- TakerPaymentSent · TakerPaymentReceived: d6efb5df6b5b01f874d9a6210d64be327b980a9354cd06c629687b4e577a16fa
- TakerPaymentSpent: 5672b8b53c16238188b5908565b2384b2a036e594e269f2773d424121e1566f5
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.