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.
73acf7901b6fd8c4e3938fa6902663e96a0dfefad6e130bef26c0bf5ae4046ad
Both payments are on their chains and locked to the same secret hash a0919be08ee72ffed19c2674d9becb59e51e5d30, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 73acf7901b6fd8c4e3938fa6902663e96a0dfefad6e130bef26c0bf5ae4046ad
- MakerPaymentSpent: 39883935d85222beb9419fdb61fc06f42bade49834c600c1aa82449b80f5146f
e2ca897351eef005daa6674dcb3b584365d16d897dee93031ed880abca3d298b
Both payments are on their chains and locked to the same secret hash a0919be08ee72ffed19c2674d9becb59e51e5d30, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6b51eaf54e9ea4ef22e26a968a2c68e744a1538637ca60291f48003ff462bfe6
- TakerPaymentSent · TakerPaymentReceived: e2ca897351eef005daa6674dcb3b584365d16d897dee93031ed880abca3d298b
- TakerPaymentSpent: 351caa699b12520bbd105a0bcfc7b0df7b8adaf693033cce82240fd33e085f79
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.