The INFORMATION_SCHEMA INNODB_TRX Table The transaction start time. The ID of the lock the transaction is currently waiting for, if  TRX_STATE  is  LOCK WAIT ; otherwise  NULL . To obtain details about the lock, join this column with the  ENGINE_LOCK_ID  column of the Performance Schema  data_locks  table. The time when the transaction started waiting on the lock, if  TRX_STATE  is  LOCK WAIT ; otherwise NULL . The MySQL thread ID. To obtain details about the thread, join this column with the  ID  column of the INFORMATION_SCHEMA PROCESSLIST  table, but see Section 15.15.2.3, “Persistence and Consistency of InnoDB Transaction and Locking Information” . The SQL statement that is being executed by the transaction. The transaction’s current operation, if any; otherwise  NULL . The number of  InnoDB  tables used while processing the current SQL statement of this transaction. The number of  InnoDB  tables that the current SQL statement has row locks on. (Because these are row locks, not table locks, the tables can usually still be read from and written to by multiple transactions, despite some rows being locked.) The number of locks reserved by the transaction. The total size taken up by the lock structures of this transaction in memory. The approximate number or rows locked by this transaction. The value might include delete-marked rows that are physically present but not visible to the transaction. The number of modified and inserted rows in this transaction. A value indicating how much work the current transaction can do before being swapped out, as specified by the  innodb_concurrency_tickets  system variable. • TRX_CONCURRENCY_TICKETS • TRX_ROWS_MODIFIED • TRX_ROWS_LOCKED • TRX_LOCK_MEMORY_BYTES • TRX_LOCK_STRUCTS • TRX_TABLES_LOCKED • TRX_TABLES_IN_USE • TRX_OPERATION_STATE • TRX_QUERY • TRX_MYSQL_THREAD_ID • TRX_WAIT_STARTED • TRX_REQUESTED_LOCK_ID 4882