traceroute - ‘traceroute’ is the universal command to
send packets to a host in a similiar fashion that ping
does, however the command displays the latency and name
for each internet hop used to reach the destination host.
‘traceroute’ is used within *NIX like operating systems
and ‘tracert’ is used within Windows based operating
systems.

To traceroute to a host within *NIX like operating systems:

traceroute <hostaddress>

examples:

traceroute 192.168.0.1
traceroute theplanet.com

example traceroute output:

traceroute russellstafford.com

traceroute to russellstafford.com (69.10.138.4, 30 hops max, 40 byte packets
1 216.234.234.2 (216.234.234.2) 0.648 ms 0.455 ms 0.398 ms
2 ibr1-ge-1-0-0-v2.dllstx3.theplanet.com (12.96.160.33) 0.726 ms 0.578 ms 0.560
3 ge-0-2-1-101.cr1.dfw1.nlayer.net (69.31.63.1) 0.836 ms 0.883 ms 0.757 ms
4 so-2-3-0.cr1.ord1.nlayer.net (69.22.142.81) 25.132 ms 25.152 ms 25.254 ms
5 rt1ec-equinix.il.shawcable.net (206.223.119.20) 26.031 ms 25.806 ms 25.608 ms
6 rc2ch-pos1-0.il.shawcable.net (66.163.65.5) 25.967 ms 25.844 ms 25.896 ms
7 rc2nr-pos14-0.wp.shawcable.net (66.163.76.173) 44.736 ms 44.211 ms 44.364 ms
8 rc1so-pos13-0.cg.shawcable.net (66.163.76.85) 60.873 ms 60.871 ms 60.846 ms
9 rc1wh-pos12-0.vc.shawcable.net (66.163.76.10) 68.862 ms 68.854 ms 69.232 ms
10 rd1ht-atm1-0-2.ok.shawcable.net (66.163.76.234) 75.936 ms 75.930 ms 75.829 ms
11 ra1ht-ge3-1.ok.shawcable.net (66.163.72.134) 76.119 ms 76.011 ms 76.226 ms
12 rx0ht-rack-force-2.ok.bigpipeinc.com (64.251.64.50) 76.489 ms 76.655 ms 76.41
13 h69-10-128-182.n-01.net (69.10.128.182) 90.152 ms 89.520 ms 88.648 ms
14 h69-10-138-48.n-01.net (69.10.138.4 89.148 ms 88.942 ms 89.168 ms

Remember, a traceroute will only show the network path being used for packets to reach the given host/destination.  To determine the network path that is used to return traffic, you will need to perform a traceroute from the destination host back to the source host.