pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,966,720
← previous block
next block →
recent activity
Analyzing
Block #101,966,720
11 transactions · 11 stateful · 2026-09-04 18:03:09 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,966,720
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
swap
· blocks 1
#2
0x5acec890
#3
0x5acec890
#4
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x6a9b0855
#10
execOrders
#5
handleOps
· blocks 1
#9
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
4 touches
1 conflict
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
0xbcc1b45913…43f94f
Audit this contract →
← previous block
·
next block →
recent activity