← previous blocknext block →recent activity

Analyzing

Block #72,296,105

13 transactions · 12 stateful · 2026-05-04 03:35:00 UTC

Parallelism

69/100

Blocked

58%

Avg conflicts / tx

0.77

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,296,105  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbb1747e2…f78b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x94cec13a…8e2f

0x065c9d…c394

4 touches
1 conflict

0x005fb969…2d97

0x34b655…2a6f

4 touches
1 conflict

0x17e2d2a0…359e

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x25e86458…ac1f

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

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 0xbb1747e217…82f78b

← previous block·next block →recent activity