pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,807,517
← previous block
next block →
recent activity
Analyzing
Block #90,807,517
12 transactions · 11 stateful · 2026-07-27 15:28:36 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,807,517
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
0xab083028
#3
deposit
#5
execFwdPositionOps
· blocks 1
#7
0xc925b3a5
#8
updateDataFeedsValuesPartial
#9
0x6a67799c
#10
approve
#11
setData
#4
0x62be7533
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
4 touches
1 conflict
0x00000000…0001
0xfa32f9…f3f0
4 touches
1 conflict
0xe90b7bce…c2e0
0xfa32f9…f3f0
4 touches
1 conflict
0x213ee207…a151
0x2b46c0…1669
2 touches
0 conflicts
0x46279ae7…20dd
0x2b46c0…1669
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
0x99f666e3cf…76b2a2
Audit this contract →
← previous block
·
next block →
recent activity