pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,960,685
← previous block
next block →
recent activity
Analyzing
Block #108,960,685
20 transactions · 18 stateful · 2026-09-29 06:06:41 UTC
Parallelism
75
/100
Blocked
50
%
Avg conflicts / tx
1
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,960,685
· 20 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#6
postStateList
#7
0x59558d29
#8
execOrders
· blocks 1
#9
updateDataFeedsValuesPartial
#10
execFwdPositionOpsV2
· blocks 3
#11
execFwdPositionOpsV2
#15
0xed82b078
#16
0xed82b078
#18
setData
#2
0x0c7abd22
· blocks 3
#12
0x84403c1b
· blocks 3
#3
0x0c7abd22
· blocks 2
#13
0x84403c1b
#14
execFwdPositionOpsV2
· blocks 2
#4
0x0c7abd22
· blocks 1
#17
execFwdPositionOpsV2
· blocks 1
#5
0x0c7abd22
#19
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w3
5
w4
8
w0
10
w0
12
w1
13
w2
14
w2
17
w3
19
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc6a8c250…737f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xf1215035…e0e5
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0057
0x1b6862…e19c
8 touches
6 conflicts
0x6bfb0678…9865
0x1b6862…e19c
8 touches
6 conflicts
0xa9c1b1d5…5e4b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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:
ShMonad (shMON)
10 conflicts on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity