← previous blocknext block →recent activity

Analyzing

Block #72,496,456

9 transactions · 9 stateful · 2026-05-05 01:49:40 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,496,456  ·  9 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xcbad3868…f129

0x34b655…2a6f

4 touches
1 conflict

0x23951077…539b

0x34b655…2a6f

4 touches
1 conflict

0x8ac7304e…589a

0x065c9d…c394

2 touches
0 conflicts

0xa11af725…3725

0x065c9d…c394

2 touches
0 conflicts

0xfc26e40d…b28c

0x065c9d…c394

2 touches
0 conflicts

0x0efc210e…70ab

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity