← previous blocknext block →recent activity
Analyzing
Block #79,407,128
34 transactions · 29 stateful · 2026-06-06 02:04:02 UTC
Parallelism
76/100
Blocked
59%
Avg conflicts / tx
1.62
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,407,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
2w04w05w06w17w28w39w410w514w016w117w418w519w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x5df6102c…6494
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
8 touches
6 conflicts
0xe0799fe7…c619
0xd32edf…ff58
7 touches
6 conflicts
0x91b02220…68f6
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
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: Perpl
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity