← previous blocknext block →recent activity

Analyzing

Block #72,296,023

18 transactions · 14 stateful · 2026-05-04 03:34:28 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,296,023  ·  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

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xcb996df5…6386

0x065c9d…c394

3 touches
1 conflict

0x5a3732cb…edac

0x1b6862…e19c

2 touches
0 conflicts

0x4bef88e0…eaca

0x3bd359…433a

2 touches
0 conflicts

0x5d82c9b5…004c

0x3bd359…433a

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

1 conflict on slot 0xbb1747e217…82f78b

← previous block·next block →recent activity