pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,966,996
← previous block
next block →
recent activity
Analyzing
Block #101,966,996
11 transactions · 9 stateful · 2026-09-04 18:04:34 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,966,996
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x59558d29
#4
updateDataFeedsValuesPartial
#5
0x000000b2
#6
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#9
setData
#10
0x000000b2
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e06d07b…36b0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe65de672…5f8f
0x34b655…2a6f
4 touches
1 conflict
0x5efd7300…d8a5
0x34b655…2a6f
4 touches
1 conflict
0x7e06d07b…36af
0x34b655…2a6f
4 touches
1 conflict
0xef3f5637…f47c
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x7e06d07b41…0636b0
Audit this contract →
← previous block
·
next block →
recent activity