pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,120,589
← previous block
next block →
recent activity
Analyzing
Block #87,120,589
9 transactions · 7 stateful · 2026-07-11 19:53:08 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,120,589
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
#2
execFwdPositionOps
· blocks 2
#3
updateDataFeedsValuesPartial
#6
0xc5a04723
#7
setData
#8
execOrders
#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
0x3b787279…727f
0x34b655…2a6f
6 touches
3 conflicts
0xe196aed0…324d
0x34b655…2a6f
4 touches
1 conflict
0xa3abf9fa…6088
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb510f9a0…ce4e
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x225e1f26…fede
0x34b655…2a6f
4 touches
1 conflict
0x2a030435…7a62
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
3 conflicts on slot
0x3b7872790d…39727f
Audit this contract →
← previous block
·
next block →
recent activity