#### 4.6.9.1 mysqlbinlog Hex Dump Format

 The [`--hexdump`](mysqlbinlog.html#option_mysqlbinlog_hexdump) option causes [**mysqlbinlog**](mysqlbinlog.html) to produce a hex dump of the binary log contents:

```
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](https://dev.mysql.com/doc/internals/en/binary-log.html).

* `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.

* `Type`: The event type code.

* `Master ID`: The server ID of the replication source server that created the event.

* `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.

