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.
b2aa8c21ae8b6c2e429da7481ff25a6e7843895e394fa2efc366e17318a171dd
Both payments are on their chains and locked to the same secret hash ed1f895ec4f7a73dcfcd7ce237852129dfb2b4c3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b2aa8c21ae8b6c2e429da7481ff25a6e7843895e394fa2efc366e17318a171dd
- MakerPaymentSpent: 2a62a5f9aa1b4cf7879f3794831bc0ddfd29bbd44b26006ed83f35e0fef3c7f0
73d48d28376b5d4880be1ebc4dc05333f2e5ab8e49ae049aba189be27f9b0917
Both payments are on their chains and locked to the same secret hash ed1f895ec4f7a73dcfcd7ce237852129dfb2b4c3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 192db297d62afbfb8fd366f3ab17d6c7968d2fe218255259063ce418411a77fe
- TakerPaymentSent · TakerPaymentReceived: 73d48d28376b5d4880be1ebc4dc05333f2e5ab8e49ae049aba189be27f9b0917
- TakerPaymentSpent: e74062f2d2a86fcf0df8d1448fd36b85f258b2a643909be3be6ee20fdaf94bc1
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.