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.
c6190e317d035e19d1026f6e803312fec92b7f7d3648b6f88960c4656740933e
Both payments are on their chains and locked to the same secret hash 2006f0d3a267d9c7d2f658f546b37b9de418664f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: c6190e317d035e19d1026f6e803312fec92b7f7d3648b6f88960c4656740933e
- MakerPaymentSpent: a21288b0cbf60011467c1de8ac5ece6be7ec7f186f0117f2728aa89818646f6b
b945ee0ffcc41b10b733ddedfed3ddc1f3c84e58c44fdea57bd0d7267e4694b8
Both payments are on their chains and locked to the same secret hash 2006f0d3a267d9c7d2f658f546b37b9de418664f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6c8c3bff7e025a76135aff733374e31debeaf3619ce64ddd46eaa3c45b2000d3
- TakerPaymentSent · TakerPaymentReceived: b945ee0ffcc41b10b733ddedfed3ddc1f3c84e58c44fdea57bd0d7267e4694b8
- TakerPaymentSpent: 51299b39e8d9bd38f52d3cb79a83276c5b75d87e4cb3d0f874726eb9c531ee9a
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.