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.
a92fd41e3d74ebefbf5c0fa0b518f96109493a18b221e42adcf9d1172318ed01
Both payments are on their chains and locked to the same secret hash da72076bcb9e52008711a350efd9547be13562f7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a92fd41e3d74ebefbf5c0fa0b518f96109493a18b221e42adcf9d1172318ed01
- MakerPaymentSpent: 697c1678cebb5215345ab9828d054d3ac314f0f0d5e87af295e794e96981b379
7aea07795ca4eeece88a6fc88dd0fbb1c56a4ba99d8f20198cb60f583716a9bb
Both payments are on their chains and locked to the same secret hash da72076bcb9e52008711a350efd9547be13562f7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a6bb7b2b64444baa5fc489d2529aa870f71c823a1541d6cd734ad47b71e466fc
- TakerPaymentSent · TakerPaymentReceived: 7aea07795ca4eeece88a6fc88dd0fbb1c56a4ba99d8f20198cb60f583716a9bb
- TakerPaymentSpent: d30047b7dff5c66fe6205f5d098f99765bf0f5189ee6a58c3bb0b21a009e5b61
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.