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.
57afa6685961695fef63e186d0cecff90fcaf1cdacca589e43ae8cc42253a3b7
Both payments are on their chains and locked to the same secret hash 3c9429cab678fcdfec55d775caafc918d6dec744, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 57afa6685961695fef63e186d0cecff90fcaf1cdacca589e43ae8cc42253a3b7
- MakerPaymentSpent: 32b6c8c2d334287f4ea61b7f16fe4e0a350bc7489a0e74ef92fbecaade306334
c83f59680f348b7dfb6b93a90225b174f52b6dda0f88b47de0887a06c5e7e6e4
Both payments are on their chains and locked to the same secret hash 3c9429cab678fcdfec55d775caafc918d6dec744, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 96770e29af19042a6b8f821e2a80079a10479f666262081c153489974196945b
- TakerPaymentSent · TakerPaymentReceived: c83f59680f348b7dfb6b93a90225b174f52b6dda0f88b47de0887a06c5e7e6e4
- TakerPaymentSpent: f4065829ae87f1c4ab1d63625a1865a2e76f4760968314bac0a2b9305547b378
Reported by kdf-statsdb-8762.