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.
1e34f9c9d34aa736562a3e4016b89e70813bbd175f394ee2d0c64936f45c5f53
Both payments are on their chains and locked to the same secret hash 72686eca6ebeb2799a9632fa522d7b056be5640e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1e34f9c9d34aa736562a3e4016b89e70813bbd175f394ee2d0c64936f45c5f53
- MakerPaymentSpent: 3dc4341cf40da90f190d68ddfd181f7c24bbed87c32268244a0ce9a54d46cd1c
072055f23de8b061b9fefabefe752ed753efd3574fce1d159ccdbef0628fafa5
Both payments are on their chains and locked to the same secret hash 72686eca6ebeb2799a9632fa522d7b056be5640e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2857ff1af496811ab0c56ce6552e7f707055371f5c697ee03b9d4d9aa2d4d864
- TakerPaymentSent · TakerPaymentReceived: 072055f23de8b061b9fefabefe752ed753efd3574fce1d159ccdbef0628fafa5
- TakerPaymentSpent: 71076f53323207c635135232705a2e8a35c115ce4177d78155e43b1a55bf8573
Reported by kdf-statsdb-8762.