← previous blocknext block →recent activity
Analyzing
Block #91,444,846
43 transactions · 41 stateful · 2026-07-29 20:58:08 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
2.72
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #91,444,846 · 43 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w28w39w010w111w012w113w214w315w416w517w618w719w821w326w227w332w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x08a39015…efa0
0x34b655…2a6f
10 touches
10 conflicts
0x4efae872…6aa8
0x34b655…2a6f
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
8 touches
6 conflicts
0xafb8e71e…9285
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity