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.
e2483d13349dd836d655819a45501b0e1f53986af9569f115aeb6572c9707490
Both payments are on their chains and locked to the same secret hash 80181732aa9a6ca5c8c47ac6b3783fcefba39602, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e2483d13349dd836d655819a45501b0e1f53986af9569f115aeb6572c9707490
- MakerPaymentSpent: 8e156acf17fa3733b4e3c703cc726593ee6f0bc10809289750fd33faf39ffff2
5d3a31c8f94b190cbc069ebb7ec823e41dd6553a0365002398d18a0667f3f237
Both payments are on their chains and locked to the same secret hash 80181732aa9a6ca5c8c47ac6b3783fcefba39602, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dc60512e8cee29777dfc9383cc68d083b96dcda2f43d3315b2eb88c2fb50caa2
- TakerPaymentSent · TakerPaymentReceived: 5d3a31c8f94b190cbc069ebb7ec823e41dd6553a0365002398d18a0667f3f237
- TakerPaymentSpent: 1816ebdb2db28b9e46fbdaccd495b163ef5b9729441e6dab74bd38d2081c76b7
Reported by kdf-statsdb-8762.