pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,696,478
← previous block
next block →
recent activity
Analyzing
Block #96,696,478
11 transactions · 9 stateful · 2026-08-17 05:48:06 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,696,478
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
execOrder
· blocks 2
#3
execOrders
#4
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#10
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff3b4736…8479
0x34b655…2a6f
6 touches
3 conflicts
0x27b96981…ef48
0x34b655…2a6f
4 touches
1 conflict
0xdc8af0c4…68f6
0x34b655…2a6f
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
4 touches
1 conflict
0xc18e56e2…abcd
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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
3 conflicts on slot
0xff3b47366b…7c8479
Audit this contract →
← previous block
·
next block →
recent activity