pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,707,440
← previous block
next block →
recent activity
Analyzing
Block #96,707,440
9 transactions · 8 stateful · 2026-08-17 06:43:14 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,707,440
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
0x3f5c179b
#4
execFwdPositionOpsV2
· blocks 2
#7
setData
#8
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x17dd6839…0f1a
0x34b655…2a6f
4 touches
1 conflict
0x3b3e5f00…9a88
0x34b655…2a6f
4 touches
1 conflict
0xfbe6a366…8ca1
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e7
0x34b655…2a6f
4 touches
1 conflict
0xa940f3a4…c5e8
0x34b655…2a6f
4 touches
1 conflict
0x0b1a9431…183e
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity