pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,512,948
← previous block
next block →
recent activity
Analyzing
Block #96,512,948
8 transactions · 7 stateful · 2026-08-16 14:25:02 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,512,948
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
#4
execFwdPositionOpsV2
#5
setData
#6
execOrders
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x75f928fc…0465
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf6322736…e546
0x34b655…2a6f
4 touches
1 conflict
0x0ef751c7…7c30
0x34b655…2a6f
2 touches
0 conflicts
0x7406a29f…4529
0x34b655…2a6f
2 touches
0 conflicts
0x7406a29f…452a
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a2
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
0xfadc118dc2…025d64
Audit this contract →
← previous block
·
next block →
recent activity