← previous blocknext block →recent activity

Analyzing

Block #73,201,926

18 transactions · 17 stateful · 2026-05-08 08:08:12 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,201,926  ·  18 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

0x3b8ffd61…f3ad

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4e5ebbf7…ae70

0xc8689a…ee79

4 touches
1 conflict

0x7f189cf6…afab

0x065c9d…c394

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x6ca43f…c331

4 touches
1 conflict

0x513d9420…8a6b

0x6ca43f…c331

4 touches
1 conflict

0xe7535190…5a0f

0x6ca43f…c331

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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 0x3b8ffd6160…92f3ad

← previous block·next block →recent activity