pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,906,908
← previous block
next block →
recent activity
Analyzing
Block #86,906,908
10 transactions · 9 stateful · 2026-07-10 20:05:38 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,906,908
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
setData
#7
0x3f5c179b
#9
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0xf6afcecb…0b92
0x34b655…2a6f
4 touches
1 conflict
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0xf0feb15e…420b
0x34b655…2a6f
4 touches
1 conflict
0x3800d0ea…6168
0x34b655…2a6f
4 touches
1 conflict
0x38befc08…20c8
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x77386f93…5748
0x34b655…2a6f
4 touches
1 conflict
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
0xae9018679a…898086
Audit this contract →
← previous block
·
next block →
recent activity