pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,309,769
← previous block
next block →
recent activity
Analyzing
Block #108,309,769
11 transactions · 10 stateful · 2026-09-26 23:25:52 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,309,769
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x59558d29
#4
0x59558d29
#5
0x3e2e8792
#6
setData
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
0x84403c1b
#10
0xc7068c7b
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7322fb4a…6359
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xc2e275bb…6914
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0009
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0002
0x1fb37a…a010
2 touches
0 conflicts
0x00000000…0009
0x1fb37a…a010
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
0x7322fb4afc…ac6359
Audit this contract →
← previous block
·
next block →
recent activity