pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,841,644
← previous block
next block →
recent activity
Analyzing
Block #111,841,644
12 transactions · 9 stateful · 2026-10-09 07:53:50 UTC
Parallelism
75
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,841,644
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
0x59558d29
#3
execOrders
· blocks 2
#6
execPerpOps
#7
execPerpOps
#8
execFwdPositionOpsV2
· blocks 1
#9
forward
#11
setData
#4
execOrders
· blocks 1
#10
execFwdPositionOpsV2
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x35b29270…6558
0x34b655…2a6f
2 touches
0 conflicts
0x62ca2979…9a50
0x34b655…2a6f
2 touches
0 conflicts
0x66ce9bfe…d5f0
0x34b655…2a6f
2 touches
0 conflicts
0x78ca0351…6ff5
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
3 conflicts on slot
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity