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.
32979e507438c2c1ee77f76de6a4854090bb893590df1ea10b73a298a80f45c1
Both payments are on their chains and locked to the same secret hash d4b486ea7cd98968b350dfc82a70e78bf39aaac0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 32979e507438c2c1ee77f76de6a4854090bb893590df1ea10b73a298a80f45c1
- MakerPaymentSpent: 675e85e3321f5c1dab051565a7d10d5bd11f1f771c0ab42d94e7c2da9b866998
5eeaf407ebaefa731816c12009f281c7ff2915da74c484db20b8d11de17860d0
Both payments are on their chains and locked to the same secret hash d4b486ea7cd98968b350dfc82a70e78bf39aaac0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fd8818baca5d269b29fd24741a94635c9d33efd612f5d8c242c990ec92461e8a
- TakerPaymentSent · TakerPaymentReceived: 5eeaf407ebaefa731816c12009f281c7ff2915da74c484db20b8d11de17860d0
- TakerPaymentSpent: e7c49608f3e322f389187349f67ed5ca6011041443014efbf969d02919c17caf
Reported by kdf-statsdb.