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.
c38bc350e8d92e833c6d046054c6e746a2b032df3a3173047af3fc0a0ec5f94f
Both payments are on their chains and locked to the same secret hash 2f32a56fc96a5ea62bea65af523259ff9f751ec2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c38bc350e8d92e833c6d046054c6e746a2b032df3a3173047af3fc0a0ec5f94f
- MakerPaymentSpent: 7f8b1c3cfc5398b070fdbfabe2a099ae4d3659bacd81b9097efb60964714e479
9ab36cca29635c2acdcc1bc2dcf3f6fc96d22067a196f34c23a4f3b8aee23ff8
Both payments are on their chains and locked to the same secret hash 2f32a56fc96a5ea62bea65af523259ff9f751ec2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3b703ec050eb9e9b2fdbb6690577b560b77ec0b7f5fd9368c6f271f1576571c3
- TakerPaymentSent · TakerPaymentReceived: 9ab36cca29635c2acdcc1bc2dcf3f6fc96d22067a196f34c23a4f3b8aee23ff8
- TakerPaymentSpent: d85124232101a07b1fb238c6441211fe9b6cf9a5688033968763eb06b93ad838
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.