pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#111,931,120
← previous block
next block →
recent activity
Analyzing
Block #111,931,120
13 transactions · 9 stateful · 2026-10-09 15:24:02 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#111,931,120
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x59558d29
#3
0x5acec890
#4
execOrders
#5
execOrders
#6
execPerpOps
#7
execPerpOps
#8
execFwdPositionOpsV2
#9
0x84403c1b
· blocks 1
#11
setData
#12
0x0c7abd22
#10
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9030597e…5bc9
0x34b655…2a6f
4 touches
1 conflict
0xe20af769…5fea
0x34b655…2a6f
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x7752d06b…b9aa
0x34b655…2a6f
4 touches
1 conflict
0x28915c4b…fac9
0x34b655…2a6f
2 touches
0 conflicts
0x4850552b…3574
0x34b655…2a6f
2 touches
0 conflicts
0x4c94c9fc…e946
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
0x9030597e81…a05bc9
Audit this contract →
← previous block
·
next block →
recent activity