← previous blocknext block →recent activity
Analyzing
Block #91,541,846
9 transactions · 7 stateful · 2026-07-30 05:06:10 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,541,846 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x351d96b9…c5df
0x34b655…2a6f
4 touches
1 conflict
0xecaa4d9e…2f88
0x34b655…2a6f
4 touches
1 conflict
0xfb874a6c…caa0
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0x09cde4ee…e38c
0x34b655…2a6f
2 touches
0 conflicts
0x1651b8d3…af6a
0x34b655…2a6f
2 touches
0 conflicts
0x34715f01…c1b1
0x34b655…2a6f
2 touches
0 conflicts
0x36a6e1a0…4d87
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x351d96b950…21c5df
Audit this contract →
← previous block·next block →recent activity