The --hexdump option causes mysqlbinlog to produce a hex dump of the binary log contents:--hexdump选项使mysqlbinlog生成二进制日志内容的十六进制转储：
mysqlbinlog --hexdump source-bin.000001
The hex output consists of comment lines beginning with 十六进制输出由以#, so the output might look like this for the preceding command:#开头的注释行组成，因此对于前面的命令，输出可能看起来像这样：
/*!40019 SET @@SESSION.max_insert_delayed_threads=0*/; /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/; # at 4 #051024 17:24:13 server id 1 end_log_pos 98 # Position Timestamp Type Master ID Size Master Pos Flags # 00000004 9d fc 5c 43 0f 01 00 00 00 5e 00 00 00 62 00 00 00 00 00 # 00000017 04 00 35 2e 30 2e 31 35 2d 64 65 62 75 67 2d 6c |..5.0.15.debug.l| # 00000027 6f 67 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |og..............| # 00000037 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| # 00000047 00 00 00 00 9d fc 5c 43 13 38 0d 00 08 00 12 00 |.......C.8......| # 00000057 04 04 04 04 12 00 00 4b 00 04 1a |.......K...| # Start: binlog v 4, server v 5.0.15-debug-log created 051024 17:24:13 # at startup ROLLBACK;
Hex dump output currently contains the elements in the following list. This format is subject to change. For more information about binary log format, see MySQL Internals: The Binary Log.十六进制转储输出当前包含以下列表中的元素。此格式可能会更改。有关二进制日志格式的更多信息，请参阅MySQL内部：二进制日志。
Position: The byte position within the log file.：日志文件中的字节位置。
Timestamp: The event timestamp. In the example shown, ：事件时间戳。在所示示例中，'9d fc 5c 43' is the representation of '051024 17:24:13' in hexadecimal.'9d fc 5c 43'是十六进制的'051024 17:24:13'的表示。
Type: The event type code.：事件类型代码。
Master ID: The server ID of the replication source server that created the event.：创建事件的复制源服务器的服务器ID。
Size: The size in bytes of the event.：事件的大小（以字节为单位）。
Master Pos: The position of the next event in the original source's binary log file.：下一个事件在原始源二进制日志文件中的位置。
Flags: Event flag values.：事件标志值。