← previous blocknext block →recent activity
Analyzing
Block #91,407,066
30 transactions · 27 stateful · 2026-07-29 17:47:00 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,407,066 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w08w09w110w211w012w113w214w315w216w317w419w525w626w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
10 touches
10 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0xdb44d160…960b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xb39cb1d8c6…28effa
Audit this contract →
← previous block·next block →recent activity