pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,650,675
← previous block
next block →
recent activity
Analyzing
Block #107,650,675
11 transactions · 10 stateful · 2026-09-24 16:07:18 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,650,675
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x59558d29
#3
updateDataFeedsValuesPartial
#4
0x84403c1b
· blocks 1
#6
execFwdPositionOpsV2
#7
transfer
#8
0x6ab54ab9
#9
setData
#10
0x0c7abd22
#5
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1393df1d…afbd
0x34b655…2a6f
4 touches
1 conflict
0x51e96b98…de36
0x34b655…2a6f
4 touches
1 conflict
0xed8224d3…528e
0x34b655…2a6f
4 touches
1 conflict
0xff1c59a7…f7d6
0x34b655…2a6f
4 touches
1 conflict
0xac799833…6da0
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
2 touches
0 conflicts
0x49890ced…6f23
0x34b655…2a6f
2 touches
0 conflicts
0xc1c014a3…805b
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
0x1393df1d34…1eafbd
Audit this contract →
← previous block
·
next block →
recent activity