pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,219,486
← previous block
next block →
recent activity
Analyzing
Block #96,219,486
11 transactions · 9 stateful · 2026-08-15 13:48:44 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,219,486
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
#3
0x5acec890
#4
forward
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#9
setData
#10
setData
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c090991…010a
0x34b655…2a6f
4 touches
1 conflict
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0xa414dec7…1b3f
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7560
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7561
0x34b655…2a6f
4 touches
1 conflict
0xc6cece75…ea3a
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
2 touches
0 conflicts
0xb0608dfe…083d
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
0x7c090991b5…92010a
Audit this contract →
← previous block
·
next block →
recent activity