pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,597,965
← previous block
next block →
recent activity
Analyzing
Block #96,597,965
8 transactions · 7 stateful · 2026-08-16 21:32:38 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,597,965
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xa96df62f
#2
0x5acec890
· blocks 1
#4
execOrders
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
#3
0x5acec890
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x2d7ea048…d78e
0x34b655…2a6f
2 touches
0 conflicts
0x344bc09a…942f
0x34b655…2a6f
2 touches
0 conflicts
0x3b00092f…cc74
0x34b655…2a6f
2 touches
0 conflicts
0x3f93c99b…f29c
0x34b655…2a6f
2 touches
0 conflicts
0x4d5891b6…bdc2
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity