pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,496,146
← previous block
next block →
recent activity
Analyzing
Block #96,496,146
9 transactions · 6 stateful · 2026-08-16 13:00:16 UTC
Parallelism
78
/100
Blocked
50
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,496,146
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
withdraw
#3
execFwdPositionOpsV2
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#4
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x28f0e082…561b
0x34b655…2a6f
2 touches
0 conflicts
0x3727225e…a3cf
0x34b655…2a6f
2 touches
0 conflicts
0x463769b9…49c9
0x34b655…2a6f
2 touches
0 conflicts
0x52bd3b34…e4e1
0x34b655…2a6f
2 touches
0 conflicts
0x5c5238c6…f2dc
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity