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.
64b38149f85eabd1b7ba3f6a8459a38b618ea5e97e40326fc79ee38909b17ceb
Both payments are on their chains and locked to the same secret hash e6f30d6be9be6820134524309c8790a26592bd4e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 64b38149f85eabd1b7ba3f6a8459a38b618ea5e97e40326fc79ee38909b17ceb
- MakerPaymentSpent: f89f10b5a41b11fbd93b27d9e0edda5110d2358681aace289dc78d444351d34c
9a17c38e89c6fe74fb4756b1606aea6b68aee4833ae01ee272ec1312d5544ccd
Both payments are on their chains and locked to the same secret hash e6f30d6be9be6820134524309c8790a26592bd4e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 064981ba8dce16a811bfedfd8568c27ab3d782db0532ee4c65b5effc28500e8f
- TakerPaymentSent · TakerPaymentReceived: 9a17c38e89c6fe74fb4756b1606aea6b68aee4833ae01ee272ec1312d5544ccd
- TakerPaymentSpent: 4e18d85d1214302690ac101221e49f080d422cb41370f5213e402cf47db51496
Reported by kdf-statsdb.