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.
c3a2773173698d5faf37a5790dcd601ad8ff2b5b66d4152be65aec67e5d74fb5
Both payments are on their chains and locked to the same secret hash 032b064bf804e83794d2100acc88f209d8fec1ce, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c3a2773173698d5faf37a5790dcd601ad8ff2b5b66d4152be65aec67e5d74fb5
- MakerPaymentSpent: 45df64915376236d2ebbe52fca629ea247eb98ba1ac6cfa76e2803d79bdebc2f
b1a8211515b914caff1b619647cbf86871a338e43cec980938535a31ba61624f
Both payments are on their chains and locked to the same secret hash 032b064bf804e83794d2100acc88f209d8fec1ce, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4d217868f1acb8b24f83f0da1d1fe274611b6438c3e94b0e89b392e0521e1605
- TakerPaymentSent · TakerPaymentReceived: b1a8211515b914caff1b619647cbf86871a338e43cec980938535a31ba61624f
- TakerPaymentSpent: 6e937136dd87f80d477c83aa9f23291f0f27a78247fdf1126c0650328fc87d87
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.