pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,205,306
← previous block
next block →
recent activity
Analyzing
Block #102,205,306
11 transactions · 10 stateful · 2026-09-05 14:12:38 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,205,306
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xcf7468f4
· blocks 1
#2
approve
· blocks 1
#5
0x59558d29
#6
updateDataFeedsValuesPartial
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
transfer
#3
swap
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0xb87af72a…aef6
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf91b744e…9117
0x754704…b603
4 touches
1 conflict
0x12c76c6b…9e93
0x3bd359…433a
4 touches
1 conflict
0xec093727…697a
0x065c9d…c394
4 touches
1 conflict
0x4dbb055a…7028
0x284f45…7777
2 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
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:
Wrapped MON (WMON)
1 conflict on slot
0x6af306bb1d…092e81
Audit this contract →
← previous block
·
next block →
recent activity