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.
2d15dc516c5a42db4c18a6b81aa10e7fe02d9343aa2eaaa12ace11f5fc4c7222
Both payments are on their chains and locked to the same secret hash ee99275a7919820ec66c445348b41062809aacad, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2d15dc516c5a42db4c18a6b81aa10e7fe02d9343aa2eaaa12ace11f5fc4c7222
- MakerPaymentSpent: 5a012eeebf5d09378a4649c49572bbe40ce23e41792b0f978a9f4531a673e009
4851ef404c9c365d2e092b03b6b7b52c653d917cf0761caa36a5067d321c219c
Both payments are on their chains and locked to the same secret hash ee99275a7919820ec66c445348b41062809aacad, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ea23658833d96662bda3536075dbf98527a57dc681e0e61871359133110cec59
- TakerPaymentSent · TakerPaymentReceived: 4851ef404c9c365d2e092b03b6b7b52c653d917cf0761caa36a5067d321c219c
- TakerPaymentSpent: a6b767c0cfdbca3da67bafe9892d6a3db628881655d5ddeb36acf4bc7cc56cbe
Reported by kdf-statsdb.