SQL Server: DBCC INPUTBUFFER to find the last statement executed by a SPID

This article is half-done without your Comment! *** Please share your thoughts via Comment ***

Are you SQL Server DBA?
Have you ever faced deadlock situations?
What are your steps to remove a deadlock?
Do you know, how to get the last statement executed by lead blocker transaction?

If you are a SQL DBA, you must know about this.
You can access few related articles:

SQL Server: Database Lock, Deadlock, Block and Isolation Interview Questions and Answers (Day-1)

SQL Server: 8 different ways to Detect a DeadLock in a Database

DBCC INPUTBUFFER:
Using this DBCC command, you can get the last statement executed by a particular SPID which is playing a lead blocker role.

Please do not blindly kill the connections by SPID. You must know the root cause of deadlock and its previous lead blocker transaction.

Prepared a one example demonstration on this.

Create a table with sample data:

Open a transaction and UPDATE one record:
Open a new session, UPDATE a same record:
Execute SP_WHO2 and find SPID of lead blocker transaction:
In my enviorment, I have found spid is: 151. You can find block by spid in BlkBy column
Execute DBCC INPUTBUFFER to find out last statement executed by SPID:
Find out lead blocker query: