This is normal for index rebuilds - or at least it is on our systems. I always found it odd that it doesn't show the actual SQL DDL query that was executed.
It will of course block unless you use the ONLINE = ON option, and that's only available in the Enterprise edition. If you're not worried about the performance impact, you can probably speed it up by changing the query to use MAXDOP = 0. That will of course be at the expense of higher CPU and IO usage.