← previous blocknext block →recent activity

Analyzing

Block #73,200,128

34 transactions · 25 stateful · 2026-05-08 07:56:13 UTC

Parallelism

76/100

Blocked

60%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,200,128  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x2a354a63…0515

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x214dc988…ba27

0x34b655…2a6f

8 touches
6 conflicts

0x251861eb…78fd

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity