← previous blocknext block →recent activity
Analyzing
Block #91,433,761
17 transactions · 17 stateful · 2026-07-29 20:02:22 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,433,761 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w311w413w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x157dbfb2…4089
0x34b655…2a6f
4 touches
1 conflict
0x1e8d3e42…f468
0x34b655…2a6f
4 touches
1 conflict
0x216bd83c…2577
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2f702750…347d
0x34b655…2a6f
4 touches
1 conflict
0x376e1d97…7d5d
0x34b655…2a6f
4 touches
1 conflict
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity