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.
2c04c422a519fa5533d86a636bfd44739cb5ce3b6697fdc345d28f4c024ef29f
Both payments are on their chains and locked to the same secret hash 0a6348335392981483dc6fed80acf96ed6c42349, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2c04c422a519fa5533d86a636bfd44739cb5ce3b6697fdc345d28f4c024ef29f
- MakerPaymentSpent: 9dd5c3f99544ca50b0705ba1a4ad66facfa3b48cdabb0899e674b302147dd644
883fa639da7ad4bbcb27a119d965504e8ffdfcc352b941d5e531a27613263b10
Both payments are on their chains and locked to the same secret hash 0a6348335392981483dc6fed80acf96ed6c42349, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 08959a36e39ee51eba444e6f9a7cc1c83896a6986077c54091655680dc285f3c
- TakerPaymentSent · TakerPaymentReceived: 883fa639da7ad4bbcb27a119d965504e8ffdfcc352b941d5e531a27613263b10
- TakerPaymentSpent: 241447079f6582e8e6aea9163047e47e06519c47c394710696fc7078d0d6f765
Reported by kdf-statsdb.