pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,542,942
← previous block
next block →
recent activity
Analyzing
Block #105,542,942
11 transactions · 9 stateful · 2026-09-17 07:14:08 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,542,942
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
0x5acec890
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#10
updateTemporalNumericValuesV1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x89ac61bf…9443
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x422eb577…203f
0x34b655…2a6f
2 touches
0 conflicts
0x625b3258…fbcd
0x34b655…2a6f
2 touches
0 conflicts
0x64061707…50c8
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
0xfd4e632c76…e1e14c
Audit this contract →
← previous block
·
next block →
recent activity