← previous blocknext block →recent activity
Analyzing
Block #91,088,691
22 transactions · 19 stateful · 2026-07-28 15:04:07 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,088,691 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w29w010w111w213w314w417w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0eb79d1…29a4
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x069b18e0…deae
0x34b655…2a6f
6 touches
3 conflicts
0x9254f7d1…2be7
0x851145…3f07
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
6 touches
3 conflicts
0x84d74093…7808
0x34b655…2a6f
6 touches
3 conflicts
0x957c875f…b3f9
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
6 conflicts on slot 0xc0eb79d1cb…5529a4
Audit this contract →
← previous block·next block →recent activity