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.
535bf536d4ad862554c42239bf552840c89441bf2ddcf8e304f2e80b61c2ca12
Both payments are on their chains and locked to the same secret hash 3f000283b72bb6ec4613d064a6adf2e2fa4ffddb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 535bf536d4ad862554c42239bf552840c89441bf2ddcf8e304f2e80b61c2ca12
- MakerPaymentReceived · 535bf536d4ad862554c42239bf552840c89441bf2ddcf8e304f2e80b61c2ca12
- MakerPaymentSpent · 271755fa7f71161fe8b276b63ff651a641767147a3657a832c1ce7f060057c56
ba0c277a39b0e4d6c6791d64286aa6739d3782bb2eb951207d4e21f17175c3ee
Both payments are on their chains and locked to the same secret hash 3f000283b72bb6ec4613d064a6adf2e2fa4ffddb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · a818554616971f35bdc474e8fc0a7023f9da02a808ef01760261f6402a6c95fb
- TakerPaymentReceived · ba0c277a39b0e4d6c6791d64286aa6739d3782bb2eb951207d4e21f17175c3ee
- TakerPaymentSpent · b4c20f04720521e72bc8b5bfe9be8fa06ef128e0a2d1b5f7ad0d16142a3c3bea
- TakerFeeSent · a818554616971f35bdc474e8fc0a7023f9da02a808ef01760261f6402a6c95fb
- TakerPaymentSent · ba0c277a39b0e4d6c6791d64286aa6739d3782bb2eb951207d4e21f17175c3ee
No anomalies were recorded against this swap.
Reported by kdf-statsdb-8762.