pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#108,619,709
← previous block
next block →
recent activity
Analyzing
Block #108,619,709
13 transactions · 13 stateful · 2026-09-28 01:26:07 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#108,619,709
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf5e395a
· blocks 1
#3
0x5acec890
#4
0xab083028
#5
0x5acec890
#6
0x5acec890
#7
execFwdPositionOpsV2
#8
0x84403c1b
#9
0x3f5c179b
#10
execFwdPositionOpsV2
#11
setData
#12
execOrders
#2
0x033bd359
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
0x4c770fe0…b972
0x3bd359…433a
4 touches
1 conflict
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0001
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0002
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0004
0x2d59fc…cd50
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:
Wrapped MON (WMON)
1 conflict on slot
0x4c770fe00c…9bb972
Audit this contract →
← previous block
·
next block →
recent activity