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.
46e3698e60905cd9254fbae8bba86d3c597191fa6a26619a9feb60782f429188
Both payments are on their chains and locked to the same secret hash 15b47ba004b55474a368a78c4cb64c754461becd, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 46e3698e60905cd9254fbae8bba86d3c597191fa6a26619a9feb60782f429188
- MakerPaymentSpent: 7fd0c00b893dd20a26388a194f9d8e57bab4b63dce517eb58aec3a1db41b5881
5ed9cefefce2dfbfc7cf6df570f3100aa4da44c0893bc6e102982d17552ab156
Both payments are on their chains and locked to the same secret hash 15b47ba004b55474a368a78c4cb64c754461becd, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bd9bb9b4f7ed26bd95f56649a6a4404f6ec29634bc2879ba3dda4f3328a3b15f
- TakerPaymentSent · TakerPaymentReceived: 5ed9cefefce2dfbfc7cf6df570f3100aa4da44c0893bc6e102982d17552ab156
- TakerPaymentSpent: 4d40433e5e8b5a16e5097ad48f48718498f2dac3ce00ce3aa2daac2de7f7f818
Reported by kdf-statsdb.