pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#120,051,517
← previous block
next block →
recent activity
Analyzing
Block #120,051,517
7 transactions · 7 stateful · 2026-11-07 01:41:44 UTC
Parallelism
71
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#120,051,517
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x35e534ea
· blocks 1
#4
0x5acec890
#6
setData
#3
0x35e534ea
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d4e5985…c97a
0x34b655…2a6f
4 touches
1 conflict
0x666889a7…968f
0x264123…670e
4 touches
1 conflict
0x33ef7909…fc8e
0x264123…670e
4 touches
1 conflict
0x0274d321…9b62
0x34b655…2a6f
2 touches
0 conflicts
0x0c7a6317…39f3
0x34b655…2a6f
2 touches
0 conflicts
0x0fd7d3aa…e1fe
0x34b655…2a6f
2 touches
0 conflicts
0x1e2ed492…b6a9
0x34b655…2a6f
2 touches
0 conflicts
0x38daab0c…c47d
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
0x9d4e598560…3bc97a
Audit this contract →
← previous block
·
next block →
recent activity