← previous blocknext block →recent activity

Analyzing

Block #73,035,207

18 transactions · 14 stateful · 2026-05-07 13:38:51 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,035,207  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7deee32f…e1d5

0xd32edf…ff58

5 touches
3 conflicts

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xad092ae6…b421

0x754704…b603

4 touches
1 conflict

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0x3a429191…9cda

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

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: 0xd32edf66…9fff58

3 conflicts on slot 0x7deee32f28…d9e1d5

← previous block·next block →recent activity