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.
541cc22422763e95e2a953e02d3ccfb77e4cc63305e495b8cd9535eff0709f8b
Both payments are on their chains and locked to the same secret hash 86cfb3699667ecd81646ebaa63524ba1ef9e48fe, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 541cc22422763e95e2a953e02d3ccfb77e4cc63305e495b8cd9535eff0709f8b
- MakerPaymentSpent: 79acc01378c41d130af8020621da81fa848e5b96d7457b286be31aa33ea486a7
bcc5cbc0abfe65119dc3f4d0da954807d2ebb25221beba2b3ac1ecc96c5508b4
Both payments are on their chains and locked to the same secret hash 86cfb3699667ecd81646ebaa63524ba1ef9e48fe, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fd3a767b94519fdd0d399d6cced652698ddd3005f9b63da8f520f766732590f4
- TakerPaymentSent · TakerPaymentReceived: bcc5cbc0abfe65119dc3f4d0da954807d2ebb25221beba2b3ac1ecc96c5508b4
- TakerPaymentSpent: d09fe54e4de7f86c9072b1d38041205dd48f8dbf1360c968f717ee11d0242381
Reported by kdf-statsdb.