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.
2058a384cd434416beb2eb736b13197225b3d0baa9052293e50ec9af3b57a1f0
Both payments are on their chains and locked to the same secret hash 10b308b650bd70a3994e65d6d44078d49afe080c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2058a384cd434416beb2eb736b13197225b3d0baa9052293e50ec9af3b57a1f0
- MakerPaymentSpent: 56394bef8bb0eb3208ec3a2707a80d7a16f4fd0980a82dac9d104ccbb6ac3860
d1c2b17312f195d8a155a67521496141d5023996d5d076ea221d9025001eba92
Both payments are on their chains and locked to the same secret hash 10b308b650bd70a3994e65d6d44078d49afe080c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b384c708e931e6bd7fc3fb8f85d0639b3125608fc90fdbe07c2e7c4be15fe20b
- TakerPaymentSent · TakerPaymentReceived: d1c2b17312f195d8a155a67521496141d5023996d5d076ea221d9025001eba92
- TakerPaymentSpent: 5acfedc8cc92d5433f93746d9e99c822b24217a6717a96328ff5b388033e48f3
Reported by kdf-statsdb-8762.