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.
d5a8fee9b23505f3a88881bb560c8c406bfb3373396a915d5ee8efa78f81a7f8
Both payments are on their chains and locked to the same secret hash 58dcd2dcbfbc724c5598f9b25f33d16548447ea2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · d5a8fee9b23505f3a88881bb560c8c406bfb3373396a915d5ee8efa78f81a7f8
c06bacad498ce3681fee0d51cf753e29c6dc10ec2997dc219db464570b6f1c02
Both payments are on their chains and locked to the same secret hash 58dcd2dcbfbc724c5598f9b25f33d16548447ea2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · cecb71290a8cbfe550a633fdd65a056f234096741ec9940c9e7404d1959b451c
- TakerPaymentReceived · c06bacad498ce3681fee0d51cf753e29c6dc10ec2997dc219db464570b6f1c02
- TakerPaymentSpent · 6e23a73a38d1ec3a2e073d15abc2b3a2cf392161ff156d32971c834416069262
Reported by kdf-statsdb.