pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,116,499
← previous block
next block →
recent activity
Analyzing
Block #96,116,499
8 transactions · 8 stateful · 2026-08-15 05:10:42 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,116,499
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
execFwdPositionOpsV2
#5
execFwdPositionOpsV2
· blocks 2
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe71e3c49…e75d
0x34b655…2a6f
6 touches
3 conflicts
0xd7d3cccb…fd18
0x34b655…2a6f
4 touches
1 conflict
0x910a6959…34b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x47ee9f76…8dee
0x34b655…2a6f
2 touches
0 conflicts
0x47ee9f76…8def
0x34b655…2a6f
2 touches
0 conflicts
0x59c989a5…b713
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
3 conflicts on slot
0xe71e3c49ad…3be75d
Audit this contract →
← previous block
·
next block →
recent activity