pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#104,976,321
← previous block
next block →
recent activity
Analyzing
Block #104,976,321
10 transactions · 10 stateful · 2026-09-15 07:42:17 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#104,976,321
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x5acec890
#4
0x928e4afa
· blocks 1
#5
0x59558d29
#6
execFwdPositionOpsV2
#8
setData
#9
execOrders
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa842b63d…fb2b
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x296d0a8a…80b5
0x34b655…2a6f
4 touches
1 conflict
0x14f03197…2dba
0x34b655…2a6f
2 touches
0 conflicts
0x5f0647bd…59b9
0x754704…b603
2 touches
0 conflicts
0xa165a1e5…67be
0x754704…b603
2 touches
0 conflicts
0xce62e150…1e09
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
0xa842b63dbc…fdfb2b
Audit this contract →
← previous block
·
next block →
recent activity