← previous blocknext block →recent activity
Analyzing
Block #91,772,382
12 transactions · 11 stateful · 2026-07-31 00:25:50 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,772,382 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7da6eb60…b34e
0x34b655…2a6f
6 touches
3 conflicts
0xaa9c420e…8b45
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5a2f19ef…f94e
0x34b655…2a6f
4 touches
1 conflict
0x5d78276c…699d
0x34b655…2a6f
4 touches
1 conflict
0x74137b07…5880
0x34b655…2a6f
4 touches
1 conflict
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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 0x7da6eb601b…b3b34e
Audit this contract →
← previous block·next block →recent activity