The transaction start time. 

• TRX_REQUESTED_LOCK_ID 

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. 

• TRX_WAIT_STARTED 

The time when the transaction started waiting on the lock, if TRX_STATE  is LOCK WAIT ; otherwise NULL . 

• TRX_MYSQL_THREAD_ID 

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” . 

• TRX_QUERY 

The SQL statement that is being executed by the transaction. 

• TRX_OPERATION_STATE 

The transaction’s current operation, if any; otherwise NULL . 

• TRX_TABLES_IN_USE 

The number of InnoDB  tables used while processing the current SQL statement of this transaction. 

• TRX_TABLES_LOCKED 

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.) 

• TRX_LOCK_STRUCTS 

The number of locks reserved by the transaction. 

• TRX_LOCK_MEMORY_BYTES 

The total size taken up by the lock structures of this transaction in memory. 

• TRX_ROWS_LOCKED 

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. 

• TRX_ROWS_MODIFIED 

The number of modified and inserted rows in this transaction. 

• TRX_CONCURRENCY_TICKETS 

A value indicating how much work the current transaction can do before being swapped out, as specified by the innodb_concurrency_tickets  system variable. 

