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.
46f442591aeb0b68d6a9106e5667d842b37aaf524da93cdc46bfa9d1c0b3cb06
Both payments are on their chains and locked to the same secret hash 391ba323742d49f987dd6652085d437cd8f199b6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 46f442591aeb0b68d6a9106e5667d842b37aaf524da93cdc46bfa9d1c0b3cb06
- MakerPaymentSpent: d35e598e35e74c6f5e49137a82d7129c5da91e172979b388ccdb379890e322f3
0ca4e3d798926089fcdbbf3d999a33d8add263d99e8de26879aeb6e09765feed
Both payments are on their chains and locked to the same secret hash 391ba323742d49f987dd6652085d437cd8f199b6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2e241a70594a95b4583ad494f4ac68b573ab12701af886167fee53657d46a271
- TakerPaymentSent · TakerPaymentReceived: 0ca4e3d798926089fcdbbf3d999a33d8add263d99e8de26879aeb6e09765feed
- TakerPaymentSpent: 3265d03aa0b0763f79630ae2f4361e6c53ca9b3e8d52baf8dceb626cdda2aeea
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.