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.
6be1420415246ce05ebeaf2a728bb7a567d0e01fe3a5839a5e1d6cac8a055546
Both payments are on their chains and locked to the same secret hash 47cda077de67595a59b20689d17a8a9448e38256, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6be1420415246ce05ebeaf2a728bb7a567d0e01fe3a5839a5e1d6cac8a055546
- MakerPaymentSpent: b83d20f0f2495c1df64b00256712525a9b26ba7bcced127e4f240e2c0cc4ddf0
23f643415d009d624f596f1135dbf0c8df93aaba08cbcfd39e4fec13339fe134
Both payments are on their chains and locked to the same secret hash 47cda077de67595a59b20689d17a8a9448e38256, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 631392a4f70fe45752ce30d695055dc524c1d34aea7af23ad4ad3f9cdddca9d8
- TakerPaymentSent · TakerPaymentReceived: 23f643415d009d624f596f1135dbf0c8df93aaba08cbcfd39e4fec13339fe134
- TakerPaymentSpent: 9f2269d7a6a261d950e185d47d7d5f47c6650b7157e91a67fe3b3ebedb9db529
Reported by kdf-statsdb.