pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,298,505
← previous block
next block →
recent activity
Analyzing
Block #92,298,505
6 transactions · 6 stateful · 2026-08-01 20:32:13 UTC
Parallelism
50
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,298,505
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
forward
#5
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03ea8e27…730f
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1534b8cf…d0fb
0x34b655…2a6f
2 touches
0 conflicts
0x217b419a…9752
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x33649c4f…b327
0x34b655…2a6f
2 touches
0 conflicts
0x37c70870…b872
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
0x03ea8e27df…ce730f
Audit this contract →
← previous block
·
next block →
recent activity