In this article We are going to INSERT a record in a simple table and try reading Transaction log record.

Note: This article is incomplete. I could not interpret lots of Hex values (no clues) and also you can expect inaccuracy in interpreted values.

USE MASTER
GO

-- Drop this database if already exists
DROP DATABASE EXPLORE_TLOG
GO

-- Create a database named Explore_TLog
CREATE DATABASE EXPLORE_TLOG
GO

USE EXPLORE_TLOG
GO

-- Create table named tEmployee

CREATE TABLE tEmployee(
 intRoll int,
 strName varchar(10),
 strDeptCode char(6),
 strCity varchar(10))
GO

-- Insert a record

BEGIN TRAN TRN_INSERT
INSERT INTO tEmployee VALUES(12345,'ABCD','DEPT01','BBBBB')
COMMIT TRAN TRN_INSERT
GO

Here is the query to fetch log record created for the above INSERT statement.

SELECT
 [RowLog Contents 0],
 [RowLog Contents 1],
 [RowLog Contents 2],
 [RowLog Contents 3],
 [LOG record]
FROM fn_dblog(null,null)
WHERE [Transaction ID] IN(
 SELECT [Transaction ID] FROM fn_dblog(null,null)
 WHERE [Transaction Name] = 'TRN_INSERT')
AND Operation = 'LOP_INSERT_ROWS'
GO

Output:

Note:

[Log record] is the *actual and compete* log record generated for our INSERTed record. You can see this record in .ldf file. 
If you closely observe, you can see values of [RowLog Contents 0] and [RowLog Contents 2] are part of [Log Record] column.

Now lets focus only on [Log record] column.

for our convenience and better clarity, lets divide [Log Record] into 3 parts:

1. Log record header

0x00003E001A0000003B000000010002006D0200000000020191000000010000
001B0000001A0000003B0000000F00000100000D000000000100000000410003
002000000014000000

2. [RowLog Content 0] - highlighted in above table.

30000E003930000044455054303104000002001B002000414243444242424242

3. [RowLog Content 2]

0101000C0000E7A4787D00000102000402030004

Interpreting Log record header:

Interpreting [RowLog Content 0]: -- This is the actual record inserted into the data page.

If you are new to data page anatomy, refer links given in part 1 of this series. 

Interpreting [RowLog Content 2]:

01 01 00 0C 00 00 E7 A4 78 7D 00 00 01 02 00 04 02 03 00 04

E7 A4 78 7D - Object Id of table tEmployee

Observation:
1. I could interpret only Object Id in this portion
2. Remaining parts [01 01 00 0C 00 00 <Object_id> 00 00 01 02 00 04 02 03 00 04] (except ObjectId) are same in 
INSERT/UPDATE/DELETE fired in user tables.

Excercise to you:

UPDATE and DELETE a record in above tExample table and and try interpreting the [Log record] content.

Summary:

The process of exprementing and confirming T-log anatomy is a huge time consuming task.
I know that this article is incomplete. Let me update this whenever I find time. 

Eagerly waiting for the review comments.