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.
9cc0f3a898533621a78c6c8476ea3cf7084d10fc86a236ac16da90dd9d13ee73
Both payments are on their chains and locked to the same secret hash 898aa56544a9f5e000fe538675f5f24d7d1cbd11, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9cc0f3a898533621a78c6c8476ea3cf7084d10fc86a236ac16da90dd9d13ee73
- MakerPaymentSpent: 880473b288383e9edfefbab163e72e78fe2ce102efc9ad1f1d18f1ab79f029ce
0adc967aeea5c0135d4062961924228c1f77c9094b571c131c2b689ebf61905d
Both payments are on their chains and locked to the same secret hash 898aa56544a9f5e000fe538675f5f24d7d1cbd11, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 822e943af3575619141bee16c82a7c3098049e768b9ca73dd5ceb9e9640d5f1a
- TakerPaymentSent · TakerPaymentReceived: 0adc967aeea5c0135d4062961924228c1f77c9094b571c131c2b689ebf61905d
- TakerPaymentSpent: ae6506d38a90a84a2b0eb10ae0c26bf4224a7576079cd45e401506251a20a737
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.