pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,307,807
← previous block
next block →
recent activity
Analyzing
Block #96,307,807
9 transactions · 9 stateful · 2026-08-15 21:12:58 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,307,807
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe33905c2
#2
execOrders
#3
0x5acec890
#4
execFwdPositionOpsV2
· blocks 1
#5
executeBatch
#7
updateDataFeedsValuesPartial
#8
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe46df8d3…e453
0x34b655…2a6f
4 touches
1 conflict
0x2c8f52ce…fe9a
0x34b655…2a6f
4 touches
1 conflict
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
2 touches
0 conflicts
0x5da59c2b…d7b2
0x34b655…2a6f
2 touches
0 conflicts
0x68d4f684…8f91
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
0xe46df8d3d3…b0e453
Audit this contract →
← previous block
·
next block →
recent activity