← previous blocknext block →recent activity

Analyzing

Block #72,285,687

13 transactions · 11 stateful · 2026-05-04 02:25:03 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,285,687  ·  13 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

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x5e9a6588…01d2

0x34b655…2a6f

2 touches
0 conflicts

0x816881fb…e436

0x34b655…2a6f

2 touches
0 conflicts

0xbad68552…e6bf

0x34b655…2a6f

2 touches
0 conflicts

0xbc04d98e…a484

0x34b655…2a6f

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

3 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity