pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,350,955
← previous block
next block →
recent activity
Analyzing
Block #84,350,955
8 transactions · 4 stateful · 2026-06-28 23:51:57 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,350,955
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
setData
#5
0x05e340…496a
#6
0x3297b9…22ed
#7
0x48c083…da9c
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x01e50701…c372
0x34b655…2a6f
2 touches
0 conflicts
0x05835d82…9130
0x34b655…2a6f
2 touches
0 conflicts
0x0c7bb1ac…7f74
0x34b655…2a6f
2 touches
0 conflicts
0x2c539d94…b63a
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…caca
0x34b655…2a6f
2 touches
0 conflicts
0x39cc2185…cacb
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity