Using this table, you can tell which transactions are waiting
        for a given lock, or for which lock a given transaction is
        waiting. This table contains one or more rows for each
        blocked transaction, indicating the lock it
        has requested and the lock(s) that is (are) blocking that
        request. The REQUESTED_LOCK_ID refers to the lock that a
        transaction is requesting, and the BLOCKING_LOCK_ID refers to
        the lock (held by another transaction) that is preventing the
        first transaction from proceeding. For any given blocked
        transaction, all rows in INNODB_LOCK_WAITS have the same value
        for REQUESTED_LOCK_ID and different values for
        BLOCKING_LOCK_ID.
      
Table 6.5. INNODB_LOCK_WAITS columns
| Column name | Description | 
|---|---|
| REQUESTING_TRX_ID | ID of the requesting transaction. | 
| REQUESTED_LOCK_ID | ID of the lock for which a transaction is waiting. Details about the
                lock can be found by joining with INNODB_LOCKSonLOCK_ID. | 
| BLOCKING_TRX_ID | ID of the blocking transaction. | 
| BLOCKING_LOCK_ID | ID of a lock held by a transaction blocking another transaction from
                proceeding. Details about the lock can be found by
                joining with INNODB_LOCKSonLOCK_ID. | 
This is the User’s Guide for InnoDB storage engine 1.1 for MySQL 5.5, generated on 2010-04-13 (revision: 19994) .

