← previous blocknext block →recent activity
Analyzing
Block #91,109,250
18 transactions · 16 stateful · 2026-07-28 16:47:34 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,109,250 · 18 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
4w07w08w19w110w211w312w313w015w116w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x7a902014…a7cf
0x40c49f…2af0
4 touches
1 conflict
0xf36f2d97…43f9
0x40c49f…2af0
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x2d651956…12e8
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 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity