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.
a7800598ef8004509c0397571ad13e16c563936d20d719bdb57cee547853fc90
Both payments are on their chains and locked to the same secret hash 06315b78e808c4515efbb584f066bb0ce2d1ae6b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a7800598ef8004509c0397571ad13e16c563936d20d719bdb57cee547853fc90
- MakerPaymentSpent: 436a7108ceb781f1d9badaa865ebeae8cc0923ba448818fc92e71ab2bc2003a3
61de69c2641b45b9dced2a91593340800cb801dd77e6e0014021dac582f59055
Both payments are on their chains and locked to the same secret hash 06315b78e808c4515efbb584f066bb0ce2d1ae6b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 17cd31fc272881b21adc5a8be07692d5f07210e3dac024be44efed105baf9d9a
- TakerPaymentSent · TakerPaymentReceived: 61de69c2641b45b9dced2a91593340800cb801dd77e6e0014021dac582f59055
- TakerPaymentSpent: afe8a5f1912c1c1ad64e99d479a35c3d181cb056412df04461d4efc3baeb0b4c
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.