pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,843,567
← previous block
next block →
recent activity
Analyzing
Block #105,843,567
14 transactions · 14 stateful · 2026-09-18 08:28:39 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,843,567
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x7d2c3ba9
#3
execOrders
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x3f5c179b
#8
execFwdPositionOpsV2
· blocks 1
#9
forward
#10
execOrders
· blocks 1
#12
0x6aacf63b
#13
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0x9210e826…1414
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdfaa9666…2003
0x34b655…2a6f
4 touches
1 conflict
0xfd7f5b55…4994
0x34b655…2a6f
4 touches
1 conflict
0x6c71e822…1263
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2b232c97…720a
0x466b47…b1e2
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
0x6d95578697…071327
Audit this contract →
← previous block
·
next block →
recent activity