pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,970,347
← previous block
next block →
recent activity
Analyzing
Block #101,970,347
12 transactions · 9 stateful · 2026-09-04 18:21:30 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,970,347
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
execute
#3
0xaebb01…4d3f
#4
matchOrders
#5
0x59558d29
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
#11
redeemDelegations
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4c059d8…185d
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4846
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4847
0x34b655…2a6f
4 touches
1 conflict
0xf74d1ad7…4e94
0x34b655…2a6f
4 touches
1 conflict
0x64275949…d698
0x34b655…2a6f
4 touches
1 conflict
0x9a9cbb1d…d272
0x34b655…2a6f
3 touches
1 conflict
0x2078936e…3597
0x754704…b603
2 touches
0 conflicts
0xe139acfb…0dda
0x754704…b603
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
0xc4c059d8f6…bf185d
Audit this contract →
← previous block
·
next block →
recent activity