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.
4a89ea64f1eb6f3ff47bb59c35632f734ad269d9da1c7d09442e2f886bcb9253
Both payments are on their chains and locked to the same secret hash 43c02cbc63cd46fc7fadecc1ee046d0c33b2528e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4a89ea64f1eb6f3ff47bb59c35632f734ad269d9da1c7d09442e2f886bcb9253
- MakerPaymentSpent: 62b0e6ec6ee576d623b609d1a46ea8f61cb1e77ddd9a5272293cf5cc3e949e71
e8542ee9c8e74137920e62dfd407878ffd99c3eb380003eca09fe86270559994
Both payments are on their chains and locked to the same secret hash 43c02cbc63cd46fc7fadecc1ee046d0c33b2528e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: c2dd6a50b729f91a2398059403a01bae0f67ca48aa84683ed14aa92363317ca3
- TakerPaymentSent · TakerPaymentReceived: e8542ee9c8e74137920e62dfd407878ffd99c3eb380003eca09fe86270559994
- TakerPaymentSpent: 8fa019b1aa066e020e69d2db264ad51d8ee7be8067dee4c66414e62dfccd5817
Reported by kdf-statsdb.