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.
457135cc0b9bb9106b320866dba55e92b40a2e23cfa82df03dcdeb1b0b3236de
Both payments are on their chains and locked to the same secret hash 3a6a35cf16405aca63858f4c0f8991533bef33b9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 457135cc0b9bb9106b320866dba55e92b40a2e23cfa82df03dcdeb1b0b3236de
- MakerPaymentSpent: 514e8867568a3ef404a60e4c18ff14d85c5846429cadeb2ae4bab0f190c507a7
887bce708a998bb386efa8f64e63ba758ec99213b1dd32f2f48b14f0e2a83ab8
Both payments are on their chains and locked to the same secret hash 3a6a35cf16405aca63858f4c0f8991533bef33b9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 75ba78ca661084ee5aaa49cc9bb2afd7972fc709b85a474d7914054c233ac779
- TakerPaymentSent · TakerPaymentReceived: 887bce708a998bb386efa8f64e63ba758ec99213b1dd32f2f48b14f0e2a83ab8
- TakerPaymentSpent: aa7f9774e44eccda3bcb6dd102b33f2849ce3f16ec857ef2677bf9971ce047ac
Reported by kdf-statsdb-8762.