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.
ab31f26e318a172a1c22aa2f1accd4447e1e0ebc0c9d6a4e77b5d09c2fbb4917
Both payments are on their chains and locked to the same secret hash 6059f0436e9016e8c861f7d740dfb01fc419c4ea, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ab31f26e318a172a1c22aa2f1accd4447e1e0ebc0c9d6a4e77b5d09c2fbb4917
- MakerPaymentSpent: 85ecdb0a17b92456def6df69b75f69a44e3e17514968d2136d81cacb00082b0c
8f44e6394dbbbf166ace68f91dbdc01ce9be912e3135825288cc7624f2b44374
Both payments are on their chains and locked to the same secret hash 6059f0436e9016e8c861f7d740dfb01fc419c4ea, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 63747f5a43b0ac4276a2a0f673b1bde780f03832911d4990e77a5c7293f42858
- TakerPaymentSent · TakerPaymentReceived: 8f44e6394dbbbf166ace68f91dbdc01ce9be912e3135825288cc7624f2b44374
- TakerPaymentSpent: 68fbf1d60886d33cf0ce6c3a4f4d4e13ce12fe55554f8fe588d5991668819034
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.