← previous blocknext block →recent activity
Analyzing
Block #92,262,171
10 transactions · 7 stateful · 2026-08-01 17:29:27 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,262,171 · 10 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfcb676f…2dea
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x88dca381…45aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xfec2fbec…91c5
0x34b655…2a6f
5 touches
3 conflicts
0xc905883b…24a6
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
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
3 conflicts on slot 0xcfcb676f70…b22dea
Audit this contract →
← previous block·next block →recent activity