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.
6da98a091ce751fb82e7796a99c8f83777498b6761aed89ccbe7fe51d536fdfc
Both payments are on their chains and locked to the same secret hash a4f7ef9e941dbab02a67938c6735ec80f278b7f1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6da98a091ce751fb82e7796a99c8f83777498b6761aed89ccbe7fe51d536fdfc
- MakerPaymentSpent: 70ae0e12404aaa34f889ea65a5c17254eca9ae226cf0e28c4ad24f2b14a5806d
00cf666e942a2c034a0dbdd72b2e3e79536fd67f71623706ebb11355dda38d6a
Both payments are on their chains and locked to the same secret hash a4f7ef9e941dbab02a67938c6735ec80f278b7f1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0bf0e529d6bf99f18bcaa1ebb1eee4ce08d089c898b0031f660bba1265b11af2
- TakerPaymentSent · TakerPaymentReceived: 00cf666e942a2c034a0dbdd72b2e3e79536fd67f71623706ebb11355dda38d6a
- TakerPaymentSpent: 6b4c0140212ef79d05f61943edd1ecbd53892746ba55c084470f309d19cc1842
Reported by kdf-statsdb.