← previous blocknext block →recent activity
Analyzing
Block #91,138,167
36 transactions · 35 stateful · 2026-07-28 19:13:01 UTC
Parallelism
92/100
Blocked
6%
Avg conflicts / tx
0.08
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,138,167 · 36 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w030w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x40d3795e…e4d7
0x34b655…2a6f
2 touches
0 conflicts
0x54526994…55b2
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity