← previous blocknext block →recent activity
Analyzing
Block #91,542,659
16 transactions · 14 stateful · 2026-07-30 05:10:16 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,542,659 · 16 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
1w03w04w15w27w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0xf583dbbf…213b
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0x746bcce3…d0ce
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xd4230a60…bd13
0x34b655…2a6f
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
10 conflicts on slot 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity