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.
119c6c95387a5776f280938235adf86f33e2d97498d1649769883b9c68da1d28
Both payments are on their chains and locked to the same secret hash f3d5e3efa089b18838a1a7ec874e2862e956b5bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 119c6c95387a5776f280938235adf86f33e2d97498d1649769883b9c68da1d28
- MakerPaymentSpent: 3297b0e5f8088d59ae20e3fc8f33e2ff470731ef7a11b00f3334bc454b85ebb0
3fb1011f24595ceeec4e4f83057deca118b92ab4cccd2f1e2de8d793ac871a50
Both payments are on their chains and locked to the same secret hash f3d5e3efa089b18838a1a7ec874e2862e956b5bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 21f3140c12cef9049dbbf2e296ac158be06725ff8a45c98b4f49cb6a3e4a1d51
- TakerPaymentSent · TakerPaymentReceived: 3fb1011f24595ceeec4e4f83057deca118b92ab4cccd2f1e2de8d793ac871a50
- TakerPaymentSpent: 555e1813af78eaa033e67e0517ccd632e7e7c5bcd1134acda41eb9ecaf79bc6b
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.