← previous blocknext block →recent activity

Analyzing

Block #74,352,275

18 transactions · 12 stateful · 2026-05-13 16:00:57 UTC

Parallelism

89/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,352,275  ·  18 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xe6455d1f…1029

0x754704…b603

4 touches
1 conflict

0x0d0b2509…074d

0x3bd359…433a

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x34857562…63ec

0x5afd3e…7620

2 touches
0 conflicts

0x835c88cb…a682

0x5afd3e…7620

2 touches
0 conflicts

0x00000000…0006

0x60bb42…87ea

2 touches
0 conflicts

0x3378e8b6…20a9

0x754704…b603

2 touches
0 conflicts

What's blocking what?

Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.

The bottleneck

Throughput-killer: 0x754704bc…afb603

1 conflict on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity