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.
9e77e7747b2c09a952c4c4de0bc2e998d380818a5ec3586e317749cba99004ee
Both payments are on their chains and locked to the same secret hash 38730b1c21961a68023af58ac265dc6e1935fabc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9e77e7747b2c09a952c4c4de0bc2e998d380818a5ec3586e317749cba99004ee
- MakerPaymentSpent: a77994fca3ac07e278ec5c1458403b194115dbb29479d6e13e8caf5caebb5b3c
1f39fffbe39450e1d3638647757001703d5d0dd19ea3c633c1daa3bfcace8354
Both payments are on their chains and locked to the same secret hash 38730b1c21961a68023af58ac265dc6e1935fabc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 360c52dc6684df09c1adbb43d914eb2e24c5ca8f74669b2ec52ce856d37a515c
- TakerPaymentSent · TakerPaymentReceived: 1f39fffbe39450e1d3638647757001703d5d0dd19ea3c633c1daa3bfcace8354
- TakerPaymentSpent: 044f26c6857e4d9311b0de8e05569b556ad5e50f6a86b3569e0699bae01db0fb
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.