pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,234,490
← previous block
next block →
recent activity
Analyzing
Block #90,234,490
9 transactions · 9 stateful · 2026-07-25 15:11:01 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,234,490
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
0x57368ddf
#3
0xce1e7030
#4
0x36f359b0
#5
transfer
#6
setData
#8
execOrders
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99137b93…c390
0x34b655…2a6f
4 touches
1 conflict
0x045502c3…b241
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0xe8cc14bb…611f
0x34b655…2a6f
4 touches
1 conflict
0x162ee430…31c3
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x330df1e6…7587
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x99137b9343…79c390
Audit this contract →
← previous block
·
next block →
recent activity