pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,991,091
← previous block
next block →
recent activity
Analyzing
Block #101,991,091
13 transactions · 13 stateful · 2026-09-04 20:06:49 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,991,091
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
0xa96df62f
#4
updatePrices
#5
execOrders
#6
0x0c7abd22
#7
updateDataFeedsValuesPartial
#8
setData
#9
execFwdPositionOpsV2
· blocks 1
#11
transfer
#12
execOrders
#2
execOrders
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
4 touches
1 conflict
0x1439cc9e…0ee8
0x34b655…2a6f
4 touches
1 conflict
0x29a58269…011a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x711ceb8d…5202
0x34b655…2a6f
4 touches
1 conflict
0x7daf6443…fd36
0x34b655…2a6f
4 touches
1 conflict
0x8849e72f…b522
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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
1 conflict on slot
0xfd713bab1a…98a651
Audit this contract →
← previous block
·
next block →
recent activity