← previous blocknext block →recent activity

Analyzing

Block #72,267,324

13 transactions · 11 stateful · 2026-05-04 00:21:37 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,267,324  ·  13 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

0x919b9826…d63f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa35098b7…c992

0x065c9d…c394

4 touches
1 conflict

0xc878d82d…699a

0x065c9d…c394

3 touches
1 conflict

0xcca6a05e…ee5f

0x065c9d…c394

3 touches
1 conflict

0xbf04f37d…85f2

0x2a68ba…90c5

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 0x919b98266b…67d63f

← previous block·next block →recent activity