pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,396,569
← previous block
next block →
recent activity
Analyzing
Block #108,396,569
13 transactions · 9 stateful · 2026-09-27 06:42:40 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,396,569
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
#2
0x59558d29
#3
0x5acec890
#4
execPerpOps
#5
execPerpOps
#6
0x0c7abd22
· blocks 1
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
#9
0xf146579f
#10
setData
#11
setData
#12
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x42102e63…8aa6
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x40b025cf…5b19
0xd32edf…ff58
3 touches
1 conflict
0x573e497e…dab5
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x8bf8d5b1…3cd5
0x34b655…2a6f
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
ShMonad (shMON)
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity