← previous blocknext block →recent activity

Analyzing

Block #73,923,881

11 transactions · 9 stateful · 2026-05-11 16:28:47 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,923,881  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xac8e97a0…8426

0x34b655…2a6f

8 touches
6 conflicts

0x9d92359d…0ca7

0x34b655…2a6f

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

8 touches
6 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x03df3a18…58e7

0x34b655…2a6f

6 touches
3 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0xac8e97a09a…ea8426

← previous block·next block →recent activity