pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,323,957
← previous block
next block →
recent activity
Analyzing
Block #98,323,957
10 transactions · 10 stateful · 2026-08-22 23:28:53 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,323,957
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x7b84f330
#3
0x6ad2e98b
#4
0xab083028
#5
0x59558d29
#6
0x928e4afa
#7
setData
#8
execFwdPositionOpsV2
· blocks 1
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64e3fa5d…8548
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0xf85bdc12…5dff
0x34b655…2a6f
4 touches
1 conflict
0xfa75029c…d62c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0x340143…768f
2 touches
0 conflicts
0x07576bbc…d54b
0x34b655…2a6f
2 touches
0 conflicts
0x113616a8…99ea
0x34b655…2a6f
2 touches
0 conflicts
0x2b5ee55a…b9ef
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
0x64e3fa5dbd…0e8548
Audit this contract →
← previous block
·
next block →
recent activity