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.
5ebdf83452e34146d8f655c0ee23129ed24ccae8b627f4e3814819778304fe05
Both payments are on their chains and locked to the same secret hash 18e5fb21bc82ab487327eef32b9ef07ac10dd9db, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5ebdf83452e34146d8f655c0ee23129ed24ccae8b627f4e3814819778304fe05
- MakerPaymentSpent: a0cffea090366f015aba34159f4e81cf3efd57f87bf44de49f87d3a4e54f3df9
2a48f83428823d0b5d7305d560d74f7948da7494589ce38ebb3d469ad2a061bc
Both payments are on their chains and locked to the same secret hash 18e5fb21bc82ab487327eef32b9ef07ac10dd9db, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ae4c6b928deae61650f324015c1f61a41d21586f0f9c5aa196b3ee3c9b941f7a
- TakerPaymentSent · TakerPaymentReceived: 2a48f83428823d0b5d7305d560d74f7948da7494589ce38ebb3d469ad2a061bc
- TakerPaymentSpent: 0a2871fbaddb493158e0b11a61ba0548ce579047191d573d8b8840f6aa564993
Reported by kdf-statsdb.