pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,308,601
← previous block
next block →
recent activity
Analyzing
Block #106,308,601
9 transactions · 8 stateful · 2026-09-19 23:30:12 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,308,601
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#4
0x59558d29
#5
setData
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#3
0x5acec890
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0xd3d054d7…4bfb
0x37db7f…ec7b
4 touches
1 conflict
0xdad13823…6798
0x37db7f…ec7b
4 touches
1 conflict
0xeb1b4ae8…64bd
0x37db7f…ec7b
4 touches
1 conflict
0x40d6d1e9…131e
0x34b655…2a6f
4 touches
1 conflict
0x547aec36…7c2b
0x34b655…2a6f
4 touches
1 conflict
0x7499cc33…a306
0x34b655…2a6f
4 touches
1 conflict
0x75f36d60…8556
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: Settlement / Helper
1 conflict on slot
0x945d1dbe12…30e1d7
Audit this contract →
← previous block
·
next block →
recent activity