pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,340,601
← previous block
next block →
recent activity
Analyzing
Block #88,340,601
9 transactions · 8 stateful · 2026-07-17 11:54:36 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,340,601
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
#2
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
· blocks 2
#4
updateDataFeedsValuesPartial
#7
0xc5a04723
#8
setData
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
6 touches
3 conflicts
0x146d0418…4ba6
0x34b655…2a6f
6 touches
3 conflicts
0x1bc07c63…d6ad
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x274ac476…27fa
0x34b655…2a6f
4 touches
1 conflict
0x53d52f6f…5520
0x34b655…2a6f
4 touches
1 conflict
0x59bfb0ed…ebd2
0x34b655…2a6f
4 touches
1 conflict
0x70f21062…b6f3
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
0x8f2033941d…ebf2db
Audit this contract →
← previous block
·
next block →
recent activity