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.
5a292a647253dcfdce3ea2991b9c963b52a0a30af2d853c82a41b5e4d2ffff3f
Both payments are on their chains and locked to the same secret hash e8f1f4ef25edf5d09a70239d804d6bf95e83594c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5a292a647253dcfdce3ea2991b9c963b52a0a30af2d853c82a41b5e4d2ffff3f
- MakerPaymentSpent: 08e2a4501eb56ec4f103cadd62e7f60b1d98d160848bf7e2fa4914f6da441057
dce1278b82c467f0fdd53f7533c21aa5b0c10edb749bded06271098a2fb474d1
Both payments are on their chains and locked to the same secret hash e8f1f4ef25edf5d09a70239d804d6bf95e83594c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 87752365e932c2792a7256e8b02f26285447c0388f020e25051c5feef7669a8b
- TakerPaymentSent · TakerPaymentReceived: dce1278b82c467f0fdd53f7533c21aa5b0c10edb749bded06271098a2fb474d1
- TakerPaymentSpent: 8bf7032770edc812baf625d91cdec06abb0ba6155a51ec14e261eb647d96dbf2
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.