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.
f1275744f7648fd46709017c7f40e2d4e08be9619eafc1f6fc275f25338ebdf1
Both payments are on their chains and locked to the same secret hash 26fb886d95cbe609a2c9917de9741379f3018401, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f1275744f7648fd46709017c7f40e2d4e08be9619eafc1f6fc275f25338ebdf1
- MakerPaymentSpent: c12fdd516befa99c040b0d4a930530449b15ba1472763254b7ad69a7b0eefd16
4cb1cada64258442ff3868fe45e7979c147c60a3b612fa0a742f1536399e8ae5
Both payments are on their chains and locked to the same secret hash 26fb886d95cbe609a2c9917de9741379f3018401, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bd8b7b3b4f6ec590434b2f62c29d44284103c2839efba1fbac02772feddfdf90
- TakerPaymentSent · TakerPaymentReceived: 4cb1cada64258442ff3868fe45e7979c147c60a3b612fa0a742f1536399e8ae5
- TakerPaymentSpent: 05182a64c408f3084702092d5122ce40581bdc4de0a01a4e89e703df6f5e7bd0
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.