pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,162,471
← previous block
next block →
recent activity
Analyzing
Block #92,162,471
11 transactions · 10 stateful · 2026-08-01 09:08:04 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
#92,162,471
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
setData
#4
0x0c7abd22
#5
0x94defb17
#7
approve
#8
0x59558d29
#9
0x4cb2db39
#10
0xc7e3ec2c
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2200019f…24f5
0x34b655…2a6f
4 touches
1 conflict
0x279ddfdc…78fb
0x34b655…2a6f
2 touches
0 conflicts
0x279ddfdc…78fc
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
2 touches
0 conflicts
0x539198ac…4d25
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity