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.
ea6feccc1b05f1e25e78b91abca4bef1def0d4c48ef1eb68841001f1a90e0299
Both payments are on their chains and locked to the same secret hash 2a39deead9fb3a7547be3d3d29e6c88afd7eea59, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ea6feccc1b05f1e25e78b91abca4bef1def0d4c48ef1eb68841001f1a90e0299
- MakerPaymentSpent: 098ba69a392eb5d0b09d5cfddf45d77885167d63205a62df82d4b9bd37ec9172
ef1551a650c1dc461f15faa0411369659178681258936ccc77ccf05e69360755
Both payments are on their chains and locked to the same secret hash 2a39deead9fb3a7547be3d3d29e6c88afd7eea59, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e1c56ba58e83af3e37aa4bfbd52f9f3d0013e67c4f7152f02321ad436db6e95f
- TakerPaymentSent · TakerPaymentReceived: ef1551a650c1dc461f15faa0411369659178681258936ccc77ccf05e69360755
- TakerPaymentSpent: 5f30469641960ff0178c2dd1a556faf3431a576dd85aea396af3d9b5a122a917
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.