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.
1db9adf64760dcaf4c754308da9d200d37c88581af775e9bd05bb8776e5340ee
Both payments are on their chains and locked to the same secret hash 72a36d1cf73c4f8659a2b89f5f481ca000a983c2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1db9adf64760dcaf4c754308da9d200d37c88581af775e9bd05bb8776e5340ee
- MakerPaymentSpent: 4944a66a79924953ae149ba8ac3f1721b9677aaadfa09df429cc4cd436399526
18845984199b0654b9f1c390f09b00ea0058ee72dc711c7db8e1644dad2e58d4
Both payments are on their chains and locked to the same secret hash 72a36d1cf73c4f8659a2b89f5f481ca000a983c2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3982fc8397745f21d32ed732eb0246aab0f98e531f8617fe3ae2588b1a1ae348
- TakerPaymentSent · TakerPaymentReceived: 18845984199b0654b9f1c390f09b00ea0058ee72dc711c7db8e1644dad2e58d4
- TakerPaymentSpent: 90077e35f8e1dd50ba7a63542ba10f89d9eb2941965cbb1bca9658404de59639
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.