pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,024,215
← previous block
next block →
recent activity
Analyzing
Block #96,024,215
8 transactions · 7 stateful · 2026-08-14 21:26:32 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,024,215
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
setData
#7
0x61d59c2d
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9c7befd…e533
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5906754f…b584
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0e22f39d…b92b
0x34b655…2a6f
4 touches
1 conflict
0xf9c7befd…e532
0x34b655…2a6f
4 touches
1 conflict
0x3a89141e…4b44
0x34b655…2a6f
3 touches
1 conflict
0xb91ace84…d2cf
0x34b655…2a6f
3 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
1 conflict on slot
0xf9c7befd83…4ce533
Audit this contract →
← previous block
·
next block →
recent activity