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.
0907d9745023456009bd641a8b5bb0feee8fd8e06275c8534988a4ba3daed18a
Both payments are on their chains and locked to the same secret hash 90b4ce5f64c3b1fb488360256ef8f11fab407932, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0907d9745023456009bd641a8b5bb0feee8fd8e06275c8534988a4ba3daed18a
- MakerPaymentSpent: 8e78b5953128367ddbc0bfceeb87ea7a200e22f583275ca9940196e41c77722f
b98a676fcece556a7c6970d1d544de33238b1485a198fff6577800fe3c601147
Both payments are on their chains and locked to the same secret hash 90b4ce5f64c3b1fb488360256ef8f11fab407932, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 875f9f93b83a3858e32d0bb81accf35e5c9a17f23dfefe342688248fbeb5ef54
- TakerPaymentSent · TakerPaymentReceived: b98a676fcece556a7c6970d1d544de33238b1485a198fff6577800fe3c601147
- TakerPaymentSpent: bdb7b076f0addd34c4efa6e6f50c5d16aba9c411f682bf7a079d96b07d57ce0a
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.