pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,207,417
← previous block
next block →
recent activity
Analyzing
Block #98,207,417
10 transactions · 8 stateful · 2026-08-22 13:42:32 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,207,417
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x41a8f47c
#2
0x41a8f47c
#3
0x6ad2e98b
#4
execOrders
#5
0x59558d29
#6
0x59558d29
#7
execFwdPositionOpsV2
· blocks 1
#9
exactInputSingle
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b2d3bee…8eec
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x10a81eed…c249
0x340143…768f
2 touches
0 conflicts
0xdc9526ab…def7
0x40c49f…2af0
2 touches
0 conflicts
0xf8f44873…7d2f
0x40c49f…2af0
2 touches
0 conflicts
0x0b552eae…fbd9
0x754704…b603
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
0x9b2d3bee9d…d68eec
Audit this contract →
← previous block
·
next block →
recent activity