← previous blocknext block →recent activity
Analyzing
Block #92,420,060
19 transactions · 17 stateful · 2026-08-02 06:43:29 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
0.79
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,420,060 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w38w411w512w413w514w616w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab1
0x34b655…2a6f
6 touches
3 conflicts
0xbf66c076…62fb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0431e51f…6f91
0x34b655…2a6f
6 touches
3 conflicts
0xdc328173…6a42
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity