pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,406,010
← previous block
next block →
recent activity
Analyzing
Block #102,406,010
10 transactions · 9 stateful · 2026-09-06 07:09:26 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,406,010
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0xab083028
#5
0xab083028
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x6a9d11a8
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc446711e…b7cb
0x99c7a7…8bf0
4 touches
1 conflict
0xc98b6062…73eb
0x754704…b603
4 touches
1 conflict
0xd1eae902…bfd4
0x754704…b603
4 touches
1 conflict
0x73bb65fc…650d
0x754704…b603
4 touches
1 conflict
0x14b2b355…8ce5
0x99c7a7…8bf0
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
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:
0x99c7a72e…c78bf0
1 conflict on slot
0xc446711ec5…89b7cb
Audit this contract →
← previous block
·
next block →
recent activity