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.
1cbed243056438ecf3579b3285184ff7e20e4ee8955b3dde9a3cf3f499466768
Both payments are on their chains and locked to the same secret hash 9f4296b92973e297e5dbb38c829dc6f465c9ae47, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1cbed243056438ecf3579b3285184ff7e20e4ee8955b3dde9a3cf3f499466768
- MakerPaymentSpent: 147cafecd3d222c81f4d8930934229fe611d1413dd71af77da499506c6e5d3ba
e5a218d53fa9ba3d15f339a3bf082dccd3b70e82414591f8da0834832f090159
Both payments are on their chains and locked to the same secret hash 9f4296b92973e297e5dbb38c829dc6f465c9ae47, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c296106a128e0c414cb2357fbc526b50fe6638656dc3eaca1cd7f0add8975d32
- TakerPaymentSent · TakerPaymentReceived: e5a218d53fa9ba3d15f339a3bf082dccd3b70e82414591f8da0834832f090159
- TakerPaymentSpent: 784a4c21b539e4c656f4e4b622ab712f62e50cdfc6147de14224312c4d21ac86
Reported by kdf-statsdb.