← previous blocknext block →recent activity
Analyzing
Block #92,332,615
12 transactions · 10 stateful · 2026-08-01 23:23:45 UTC
Parallelism
58/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,332,615 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0xe2b888e1…9374
0x34b655…2a6f
5 touches
3 conflicts
0x378d61e4…7f15
0x34b655…2a6f
4 touches
1 conflict
0x60121123…a194
0x34b655…2a6f
3 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 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity