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.
523f455dd9d55ef347a3d946c84aedc2e047a74beaa1e5135b3ef10d24147181
Both payments are on their chains and locked to the same secret hash a4197b96b30a6c98863e2559d18cd39f26229f19, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 523f455dd9d55ef347a3d946c84aedc2e047a74beaa1e5135b3ef10d24147181
- MakerPaymentSpent: 74830c26aaffd8d3831881874f2bc90cbc202aaf9e55c8d825a54676ad0845b3
3f18654cf9037756923162e342ab11216323d356f4f8b6a1ba05ba5418137a27
Both payments are on their chains and locked to the same secret hash a4197b96b30a6c98863e2559d18cd39f26229f19, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: cd231e10404d1d38e6c693c404156120b2ac4a8ffe8afbd3c621d32108553448
- TakerPaymentSent · TakerPaymentReceived: 3f18654cf9037756923162e342ab11216323d356f4f8b6a1ba05ba5418137a27
- TakerPaymentSpent: 59ab0885cdb54073ce34cc3c7bb5b933c79b249f3f122fe405af48d6a82809bc
Reported by kdf-statsdb.