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.
8676fb22db969d58b25ce8e935e526b7eafcc644035c42aa8c5b9b9c2625c37f
Both payments are on their chains and locked to the same secret hash de14f893ed8943151c3870c773af7b46e144c5bf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8676fb22db969d58b25ce8e935e526b7eafcc644035c42aa8c5b9b9c2625c37f
- MakerPaymentSpent: 4ca234cdb81374150e35b692a410f43a6e5f2c0d711a85a59fdebc1b709bc2a7
f3dd87b3fae1b2466faa5ff4a6411dcf914043a883399edcb11a2d8807adf7e5
Both payments are on their chains and locked to the same secret hash de14f893ed8943151c3870c773af7b46e144c5bf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: a03c03c96d3a619780699808fcaf6afc347c5f76e60954f9dca4dd01a476acfd
- TakerPaymentReceived · TakerPaymentSent: f3dd87b3fae1b2466faa5ff4a6411dcf914043a883399edcb11a2d8807adf7e5
- TakerPaymentSpent: fcdd347f1c1328257201b0d220eab1ac8f7493877bff3d94fe5e05d83df666e1
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.