← previous blocknext block →recent activity
Analyzing
Block #91,161,038
11 transactions · 11 stateful · 2026-07-28 21:08:05 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,161,038 · 11 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x802738ef…9072
0x34b655…2a6f
4 touches
1 conflict
0x26dda7d6…8c4d
0x34b655…2a6f
2 touches
0 conflicts
0x36ccd82a…7be7
0x34b655…2a6f
2 touches
0 conflicts
0x3e2663d3…a620
0x34b655…2a6f
2 touches
0 conflicts
0x46870010…0b51
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity