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.
78607d6a82fedb5ac8ec5995e0fc3ee4dc28c19634851ab6669a7be549dca92a
Both payments are on their chains and locked to the same secret hash 56da7323e11b18c47d08ad1f134885c66a5458c4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 78607d6a82fedb5ac8ec5995e0fc3ee4dc28c19634851ab6669a7be549dca92a
- MakerPaymentSpent: b4a1ff7696884379d69bc0d26371effd29e62fff22fa39f96bf5cbf34c3e9b23
d3d5a0d09e65c1118905c9e6e9e32425193cd934787f127c57f30262627eab82
Both payments are on their chains and locked to the same secret hash 56da7323e11b18c47d08ad1f134885c66a5458c4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d6c8f2e5d456b28f4298e23ff72dfee6164234a8b8c3959fc9551ed176fee94
- TakerPaymentSent · TakerPaymentReceived: d3d5a0d09e65c1118905c9e6e9e32425193cd934787f127c57f30262627eab82
- TakerPaymentSpent: 8ed8c898bbfda5a1e18bf33c567744bd18dd2283465d0f9ed07a3e61d4258d59
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.