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.
0124a8e4717538ca41e4f2bd6e5b9d5dd0eb0809dbe3cd18684398f4414bae0a
Both payments are on their chains and locked to the same secret hash b9f305843bfa11ced175cefff47ca294a7353b19, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0124a8e4717538ca41e4f2bd6e5b9d5dd0eb0809dbe3cd18684398f4414bae0a
- MakerPaymentSpent: 0bb1cdf15ea3acdabb072f3692b0180c2c12148dedf24f38b52c154b5b8e7eb4
a7e3b01ac76982fc94d225fba7930dc84feec6e1d1e23dedfdf0d1919bbb1bb9
Both payments are on their chains and locked to the same secret hash b9f305843bfa11ced175cefff47ca294a7353b19, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5f150c66224adf85204a704de341758b427ee79fb0128b0a45bb861dcb7a64be
- TakerPaymentReceived · TakerPaymentSent: a7e3b01ac76982fc94d225fba7930dc84feec6e1d1e23dedfdf0d1919bbb1bb9
- TakerPaymentSpent: 9de373d79c9b803aee8b5bff4ae4d2e704b67c6497f548375e80cf7aca8f732c
Reported by kdf-statsdb.