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.
2b32bfd8a74cf73becc2f00f75c3f0f636532a56d5611d0c9b7e67b35b2523ce
Both payments are on their chains and locked to the same secret hash 6f6c789a1a8f989d46931ce85ea38835336e7107, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2b32bfd8a74cf73becc2f00f75c3f0f636532a56d5611d0c9b7e67b35b2523ce
- MakerPaymentSpent: 5fd30eb650e35fb24b4f3ec564e9213c6c2527f485a17aa1126f421f578aceb9
b0ba3e20476039927085389155d60aaa3de25ccbb227e87166285e14a18ec702
Both payments are on their chains and locked to the same secret hash 6f6c789a1a8f989d46931ce85ea38835336e7107, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: afc5927366761a30e4eade84b3e9ede8f66dfcef04543edfb5c32fc741c68ef0
- TakerPaymentSent · TakerPaymentReceived: b0ba3e20476039927085389155d60aaa3de25ccbb227e87166285e14a18ec702
- TakerPaymentSpent: 98b2e91a94549e5a03ca22c5d4d7590774a626c2f14c07416b39ae8b75ae2961
Reported by kdf-statsdb.