← previous blocknext block →recent activity

Analyzing

Block #72,296,100

12 transactions · 9 stateful · 2026-05-04 03:34:58 UTC

Parallelism

83/100

Blocked

11%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,100  ·  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

0x2c9afded…d0c9

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x48882d76…732d

0x065c9d…c394

3 touches
1 conflict

0x0a2f0381…6be8

0x065c9d…c394

3 touches
1 conflict

0x3d179c4c…cfd6

0x065c9d…c394

2 touches
0 conflicts

0x49847189…eff2

0x065c9d…c394

2 touches
0 conflicts

0x94cec13a…8e2f

0x065c9d…c394

2 touches
0 conflicts

0xcdd37631…4fee

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x2c9afded29…0cd0c9

← previous block·next block →recent activity