pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,662,773
← previous block
next block →
recent activity
Analyzing
Block #101,662,773
11 transactions · 11 stateful · 2026-09-03 16:31:06 UTC
Parallelism
64
/100
Blocked
27
%
Avg conflicts / tx
0.45
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,662,773
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
transfer
#2
execOrders
· blocks 3
#5
0x59558d29
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
setData
#3
execOrders
· blocks 1
#4
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
10
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf7772b49…fc12
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0x987859be…2686
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x31102221…9952
0x34b655…2a6f
6 touches
3 conflicts
0x6823c28e…594c
0x34b655…2a6f
6 touches
3 conflicts
0x4ffa3adf…7ab2
0x34b655…2a6f
6 touches
3 conflicts
0xd98afa6e…3364
0x34b655…2a6f
6 touches
3 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
3 conflicts on slot
0xf7772b4910…d2fc12
Audit this contract →
← previous block
·
next block →
recent activity