← previous blocknext block →recent activity

Analyzing

Block #73,962,734

12 transactions · 6 stateful · 2026-05-11 20:47:11 UTC

Parallelism

83/100

Blocked

17%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,962,734  ·  12 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

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x33f2d9b1…b689

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x5e6f50d0…28c5

0x34b655…2a6f

2 touches
0 conflicts

0x638f0a84…a8ac

0x34b655…2a6f

2 touches
0 conflicts

0x9ea57326…329f

0x34b655…2a6f

2 touches
0 conflicts

0xb91a6f59…722c

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 0xf6476f21e7…f83580

← previous block·next block →recent activity