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.
f1d94eeb5c2e6edb758dd1704eb524dab2b5220afe1506bd2c4bff300f592344
Both payments are on their chains and locked to the same secret hash 93f1366e782b7af485e79536d439ef654605745c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f1d94eeb5c2e6edb758dd1704eb524dab2b5220afe1506bd2c4bff300f592344
- MakerPaymentSpent: fba614067898662a178457209d86df147877cb1521e87f4a8c5544b2a7ddc5fc
359a195365c34b329f7128c58652e9ad27c64f914dc672999fc04dd63969a299
Both payments are on their chains and locked to the same secret hash 93f1366e782b7af485e79536d439ef654605745c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0a83a65269d6a0fd71297a15120a588ea2d28a24757d7bb346000508c085c960
- TakerPaymentSent · TakerPaymentReceived: 359a195365c34b329f7128c58652e9ad27c64f914dc672999fc04dd63969a299
- TakerPaymentSpent: b51a9428aea624c78daf5b33d40218ee8e742f1adc7b0d3c7019e9c252823aef
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.