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.
17381360841f3c9d28df657d58eb533dc6c7deb551b06ca7acd745d72a9d9823
Both payments are on their chains and locked to the same secret hash 4ce57abd1eb78906c26a97cf5502c1597f984312, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 17381360841f3c9d28df657d58eb533dc6c7deb551b06ca7acd745d72a9d9823
- MakerPaymentSpent: c555832ecbe54f149ddf4c83c2efcd8bb2ae111b10d28bc830f68cc6930af98f
26968acbbbe478ac6b8174db05ee61e173e027c4d814f494ab1e6722c098ad89
Both payments are on their chains and locked to the same secret hash 4ce57abd1eb78906c26a97cf5502c1597f984312, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1ee7d0c432fe7bb2213066f859c8307d9f664d5e2d791b96fe15775a7419e676
- TakerPaymentSent · TakerPaymentReceived: 26968acbbbe478ac6b8174db05ee61e173e027c4d814f494ab1e6722c098ad89
- TakerPaymentSpent: 3bf479cdde5edd66e8a1d1db5c90c10e0d082081396ec8d3e013973b1eabb886
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.