pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,832,926
← previous block
next block →
recent activity
Analyzing
Block #111,832,926
10 transactions · 8 stateful · 2026-10-09 07:09:59 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,832,926
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0x59558d29
#4
0x59558d29
#5
execOrders
#6
execOrders
#7
verifyOracleProofV2
#8
execFwdPositionOpsV2
#9
setData
#2
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x104ba9ff…e81d
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x167e0335…4f8b
0x34b655…2a6f
4 touches
1 conflict
0x5e47e272…4986
0x34b655…2a6f
4 touches
1 conflict
0xb2a13302…985a
0x34b655…2a6f
4 touches
1 conflict
0xc853be2d…b18f
0x34b655…2a6f
4 touches
1 conflict
0xd5208c2b…dc3d
0x34b655…2a6f
4 touches
1 conflict
0xf0099e9f…535d
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
1 conflict on slot
0x104ba9ff7d…4de81d
Audit this contract →
← previous block
·
next block →
recent activity