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.
b1165692cd882bf6a5aaead1e92b40dc2eff275bef70d42e08db91d36f2039ba
Both payments are on their chains and locked to the same secret hash 00c31d230edc37f33ff2310e1aca740c44b18904, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b1165692cd882bf6a5aaead1e92b40dc2eff275bef70d42e08db91d36f2039ba
- MakerPaymentSpent: 5f140b0d25eca42f2636eb61c77df9dea37c41b61c3ee57621f9bee941bcf700
775981d23db86571b2717cbbdb74c949138ef2fa725dfdd2fe9cdf0b1843e7c0
Both payments are on their chains and locked to the same secret hash 00c31d230edc37f33ff2310e1aca740c44b18904, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4f5d3b6c55627d95f266a7ef36a763ad04281059cceda9abae4b70a5163e2815
- TakerPaymentSent · TakerPaymentReceived: 775981d23db86571b2717cbbdb74c949138ef2fa725dfdd2fe9cdf0b1843e7c0
- TakerPaymentSpent: 17ff6f0d802822ac8376eeb056a03a53a2a7b03fabfe22ec21f33570dc9e84c5
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.