← previous blocknext block →recent activity

Analyzing

Block #74,562,569

11 transactions · 11 stateful · 2026-05-14 15:26:12 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,562,569  ·  11 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

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x220f4f84…15f8

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0de7749d…5bef

0x34b655…2a6f

2 touches
0 conflicts

0x0e903356…3d5b

0x34b655…2a6f

2 touches
0 conflicts

0x16867f4f…0bb3

0x34b655…2a6f

2 touches
0 conflicts

0x2ac7f66e…e903

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0x6eba5e7f6a…ac4b52

← previous block·next block →recent activity