pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,383,323
← previous block
next block →
recent activity
Analyzing
Block #95,383,323
8 transactions · 6 stateful · 2026-08-12 15:40:15 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,383,323
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execOrders
· blocks 2
#3
updateDataFeedsValuesPartial
#6
setData
#7
0xbb7854…ba04
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5774c048…a7f5
0x34b655…2a6f
6 touches
3 conflicts
0x226ae29a…2612
0x34b655…2a6f
4 touches
1 conflict
0xc755c95b…6814
0x34b655…2a6f
4 touches
1 conflict
0x0cd89b3c…836c
0x34b655…2a6f
2 touches
0 conflicts
0x442e26a3…e968
0x34b655…2a6f
2 touches
0 conflicts
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x5a2308ac…0983
0x34b655…2a6f
2 touches
0 conflicts
0x6771eae2…7014
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
0x5774c04887…1da7f5
Audit this contract →
← previous block
·
next block →
recent activity