pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,815,504
← previous block
next block →
recent activity
Analyzing
Block #107,815,504
11 transactions · 11 stateful · 2026-09-25 05:58:15 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,815,504
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x59558d29
#3
0xab083028
#4
0x3f5c179b
#5
execFwdPositionOpsV2
#6
forward
#7
0x84403c1b
· blocks 1
#9
updateDataFeedsValuesPartial
#10
setData
#8
0x84403c1b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x3ea25e92…a36d
0x34b655…2a6f
4 touches
1 conflict
0xa23b9051…392f
0x34b655…2a6f
4 touches
1 conflict
0x083b2564…ee27
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0009
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x6fd9ae7c…e984
0x1b6862…e19c
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
0x2328941c9c…fc84d3
Audit this contract →
← previous block
·
next block →
recent activity