Block #72,309,922

← previous blocknext block →recent activity

Analyzing

Block #72,309,922

12 transactions · 11 stateful · 2026-05-04 05:07:05 UTC

Parallelism

75/100

Blocked

18%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,309,922  ·  12 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5f7064fd…fa0f

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x55c44db6…140c

0x065c9d…c394

3 touches
1 conflict

0xc518273f…f2ed

0x065c9d…c394

3 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0x031f2869…2b32

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity