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.
8eb5e13aee44f5ccc83c3f9086df16c6264ab79df0091cb23ec37b6afd72c35c
Both payments are on their chains and locked to the same secret hash 46f5cd4a0e2b6c0a44b040aebbade68b4f813dd5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 8eb5e13aee44f5ccc83c3f9086df16c6264ab79df0091cb23ec37b6afd72c35c
32ea4225b4931a8131655016d6f5f3559fbfa271d6c7e6ce4114d4e0fcb4e7a7
Both payments are on their chains and locked to the same secret hash 46f5cd4a0e2b6c0a44b040aebbade68b4f813dd5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 89ed6015fa5f1c5810c4264848bcedc7ca42a18d5c71b7976b6e7354f2fb9658
- TakerPaymentReceived: 32ea4225b4931a8131655016d6f5f3559fbfa271d6c7e6ce4114d4e0fcb4e7a7
- TakerPaymentSpent: 63b615c714c73eba023b11672920b401b75c578e07b7b934e85553aaca0679dd
Reported by kdf-statsdb.