pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#110,380,083
← previous block
next block →
recent activity
Analyzing
Block #110,380,083
11 transactions · 10 stateful · 2026-10-04 05:13:52 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
#110,380,083
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
execOrders
#3
0x928e4afa
#4
execPerpOps
#5
execPerpOps
#6
0x013b6436
#7
execFwdPositionOpsV2
· blocks 1
#8
0x0c7abd22
#9
setData
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c211514…b757
0x34b655…2a6f
4 touches
1 conflict
0x7a093de7…f590
0x34b655…2a6f
4 touches
1 conflict
0xb4656137…5858
0x34b655…2a6f
4 touches
1 conflict
0x8fb43402…67e9
0x154be7…a638
2 touches
0 conflicts
0x8fb43402…67ea
0x154be7…a638
2 touches
0 conflicts
0x09ac6db5…4906
0x34b655…2a6f
2 touches
0 conflicts
0x1e737223…2278
0x34b655…2a6f
2 touches
0 conflicts
0x1f396cee…862f
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
0x8c21151476…60b757
Audit this contract →
← previous block
·
next block →
recent activity