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.
85587b9e8b5ca77609c096bf2e9557fc07117c5d3014e093b3755d148e25e0bc
Both payments are on their chains and locked to the same secret hash 201683dfef225cc9952c3fdc91e9f4e37f4d41c6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 85587b9e8b5ca77609c096bf2e9557fc07117c5d3014e093b3755d148e25e0bc
- MakerPaymentSpent: 2817858b9970df2b8a9678b4e735f858e77edebd5a32b67fa00e41cd3bccf87a
94e9f533b60e9e49b430c11acf5ab3aa4b027b09a9a8a64f5027848ce707bd5a
Both payments are on their chains and locked to the same secret hash 201683dfef225cc9952c3fdc91e9f4e37f4d41c6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7fc375ee9fec9511050ba783979b196f7fe523a6bd8241515a70239626870755
- TakerPaymentSent · TakerPaymentReceived: 94e9f533b60e9e49b430c11acf5ab3aa4b027b09a9a8a64f5027848ce707bd5a
- TakerPaymentSpent: c0382d20a64b2674f4fbed59c7f91cc6a23b91f6cdb944ec11af0b12d61d11d5
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.