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.
d9d902a43c113d83844371cf2a4298f73bb3662f0cc32a75f389b111589d6138
Both payments are on their chains and locked to the same secret hash eb6aea8cf96f9479eb08634568f8a4f3dac0dc4c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · d9d902a43c113d83844371cf2a4298f73bb3662f0cc32a75f389b111589d6138
02da6e3e7ae3b4964ecda8e437c6a9bcc48246c3f15b23f6a576f008b0c17d11
Both payments are on their chains and locked to the same secret hash eb6aea8cf96f9479eb08634568f8a4f3dac0dc4c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 53bb6f6ae58ee13fe8ec443833b8476d777e2604d3f6b24e25ce0f7ac82db79f
- TakerPaymentReceived · 02da6e3e7ae3b4964ecda8e437c6a9bcc48246c3f15b23f6a576f008b0c17d11
- TakerPaymentSpent · 5310e5e76cd44e223b018fc68c0aa206cc05d2dcfd9d9ae9f5140afe6ae7a678
Reported by kdf-statsdb.