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.
0515b1aac7533103d2563478ec96a234387a5bbb1cb98bc9405cb09171f3531b
Both payments are on their chains and locked to the same secret hash bb0ad92fc39d3619756202405e846c9e0e36cf19, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0515b1aac7533103d2563478ec96a234387a5bbb1cb98bc9405cb09171f3531b
- MakerPaymentSpent: 4006545616d5d3e2262f071b783ba0ea698cb70a83c7e06588b88d4cdc3f0418
37641756c1a745c06b09c543e91716ff3647719833387e6fa2662d6a692fe0a1
Both payments are on their chains and locked to the same secret hash bb0ad92fc39d3619756202405e846c9e0e36cf19, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3a981894b92893a089c66061dd26b965281a46dd1ce958b65dac8d47171b1b61
- TakerPaymentSent · TakerPaymentReceived: 37641756c1a745c06b09c543e91716ff3647719833387e6fa2662d6a692fe0a1
- TakerPaymentSpent: 05c779e517737ee02c4d40ecefc3e0e414cec152df1fbdf02ca8e052fa8de349
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.