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.
9f02f3a4f5abda64271395fb3f7be9a4a77312814ac7638ee4b4c50c1de61230
Both payments are on their chains and locked to the same secret hash 2b78038d236ab340fb86e50de0763d57d57580e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 9f02f3a4f5abda64271395fb3f7be9a4a77312814ac7638ee4b4c50c1de61230
- MakerPaymentReceived · 9f02f3a4f5abda64271395fb3f7be9a4a77312814ac7638ee4b4c50c1de61230
- MakerPaymentSpent · d24528c17ebd66ad666a9805a4a532d7fceb734a9153895616bad5c8358338cc
f5963402f0a682d4e4c3cacb143e6c61b38d28cd245256da11713d48be2f2bd4
Both payments are on their chains and locked to the same secret hash 2b78038d236ab340fb86e50de0763d57d57580e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 7af670ecf6992915974e346e560d4441f930d3307d3293fb988e716e10d462b8
- TakerPaymentReceived · f5963402f0a682d4e4c3cacb143e6c61b38d28cd245256da11713d48be2f2bd4
- TakerPaymentSpent · b2cf87c419367d103e074c7a7066d9e7d7c62b1680088702400f566cf2b0ce53
- TakerFeeSent · 7af670ecf6992915974e346e560d4441f930d3307d3293fb988e716e10d462b8
- TakerPaymentSent · f5963402f0a682d4e4c3cacb143e6c61b38d28cd245256da11713d48be2f2bd4
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.