I think I figured it out. I'll need to wait for the next time we have an issue.
This is what I found that helped
https://msdn.microsoft.com/en-us/library/ms179881.aspx
http://www.sqlservercentral.com/articles/Blocking/73148/
/*
The query results will return all active transactions and connections on the SQL Server involved in blocking, identified by SPIDs.
If no blocking exists, the query will return no results.
The blocked column will show which transaction is doing the blocking of the other transaction(s).
There is often a long running chain where SPID X is blocked by SPID Y which is blocked by SPID Z.
This is only able to trap real time blocking.
*/
select spid, blocked, waittype
, waittime, lastwaittype, dbid
, uid, cpu, physical_io, memusage
, login_time, last_batch, hostname
, program_name, nt_domain, nt_username, loginame
from master..sysprocesses
where blocked <> 0
or spid in (select blocked from master..sysprocesses)
Thanks ... and have a Great day!