pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,681,105
← previous block
next block →
recent activity
Analyzing
Block #101,681,105
9 transactions · 8 stateful · 2026-09-03 18:03:19 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,681,105
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xaa1772…d79b
#2
execute
#3
updatePrices
#4
execFwdPositionOpsV2
· blocks 2
#6
execFwdPositionOpsV2
#8
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf15273a1…2c52
0x34b655…2a6f
6 touches
3 conflicts
0x174ec0d3…8d7b
0x34b655…2a6f
6 touches
3 conflicts
0xfb856b8c…7557
0x34b655…2a6f
4 touches
1 conflict
0xfb856b8c…7558
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4dcfa6d3…81fc
0x34b655…2a6f
4 touches
1 conflict
0x805d08cf…3cfc
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
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
3 conflicts on slot
0xf15273a148…932c52
Audit this contract →
← previous block
·
next block →
recent activity