← previous blocknext block →recent activity
Analyzing
Block #91,386,596
13 transactions · 11 stateful · 2026-07-29 16:03:50 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,386,596 · 13 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63f46ea6…18c4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x02878015…aba9
0x34b655…2a6f
2 touches
0 conflicts
0x045502c3…b241
0x34b655…2a6f
2 touches
0 conflicts
0x1febc2d0…0136
0x34b655…2a6f
2 touches
0 conflicts
0x4e782273…1690
0x34b655…2a6f
2 touches
0 conflicts
0x5bb46f6c…7693
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 0x63f46ea6ba…5318c4
Audit this contract →
← previous block·next block →recent activity