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.
d3c379b7687f6b69fcb79a06f8f9683e67f9c46face481ee4b207db61f0d0a20
Both payments are on their chains and locked to the same secret hash 6feff6172c3ff63041d2fc58b707df5be6c00200, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d3c379b7687f6b69fcb79a06f8f9683e67f9c46face481ee4b207db61f0d0a20
- MakerPaymentSpent: 0d4665fd80375e72558171ad0f909acf7e954aa1890168227ff00fd3c43758f5
188289679def44e2c27695f4566e45cb47818fba27d4a62a74f1883025149935
Both payments are on their chains and locked to the same secret hash 6feff6172c3ff63041d2fc58b707df5be6c00200, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 00d977629ce9e42b1a44aa33f4084ab8e795659203ce4d89dd716a9c0658ac9d
- TakerPaymentSent · TakerPaymentReceived: 188289679def44e2c27695f4566e45cb47818fba27d4a62a74f1883025149935
- TakerPaymentSpent: 30ed387e72a5571f317283afc19423eb7a16d3cbf1d3f9d22bf8343358f63ce3
Reported by kdf-statsdb-8762.