← previous blocknext block →recent activity

Analyzing

Block #72,309,629

9 transactions · 9 stateful · 2026-05-04 05:05:08 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,309,629  ·  9 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x0a892d30…2ba2

0x065c9d…c394

2 touches
0 conflicts

0x4c44ea98…59af

0x065c9d…c394

2 touches
0 conflicts

0x625550a4…80a2

0x065c9d…c394

2 touches
0 conflicts

0xc73a42c1…6282

0x065c9d…c394

2 touches
0 conflicts

0x9f0eb83e…6daf

0x1001ff…1001

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity