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.
dc946f789420ea56c5b9acf3ed37a0151c243ab018c5fb9f53ae8fb2aa151f45
Both payments are on their chains and locked to the same secret hash bb41093f47addebcb42b3d6c16b2dc67da328ed0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dc946f789420ea56c5b9acf3ed37a0151c243ab018c5fb9f53ae8fb2aa151f45
- MakerPaymentSpent: 410b4a10a72b2af7ce05a3c178fe25a63264c65825723aa2a01228adc41cebaf
675149b4b458ac0d08d2ef6c6eece8de67f60c86070a13a421e11f74bef71610
Both payments are on their chains and locked to the same secret hash bb41093f47addebcb42b3d6c16b2dc67da328ed0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e984c6da58854ee26bb50c674abc9e073512424202af556e41dc72cfa98b907c
- TakerPaymentSent · TakerPaymentReceived: 675149b4b458ac0d08d2ef6c6eece8de67f60c86070a13a421e11f74bef71610
- TakerPaymentSpent: edc52d8b2d0d7b11ae6f207b4ea6ed99f708fcbd31ed1846b8a42c765f2c5ea6
Reported by kdf-statsdb.