← previous blocknext block →recent activity
Analyzing
Block #95,150,135
42 transactions · 38 stateful · 2026-08-11 19:55:00 UTC
Parallelism
62/100
Blocked
68%
Avg conflicts / tx
2.1
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #95,150,135 · 42 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
1w02w03w04w16w07w18w29w310w111w214w518w621w326w929w1032w233w334w135w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
12 touches
15 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
10 touches
10 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x4c619b7d…f4fa
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
15 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity