pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,607,032
← previous block
next block →
recent activity
Analyzing
Block #84,607,032
11 transactions · 8 stateful · 2026-06-30 04:19:47 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,607,032
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x6ad2e98b
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x39435dac
#6
executeBatch
#7
setData
#8
exactInputSingle
#9
0x0f6795d9
· blocks 1
#10
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee28d8b5…bd37
0x34b655…2a6f
4 touches
1 conflict
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x3ed63e00…786e
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe560375e…4626
0x34b655…2a6f
4 touches
1 conflict
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
0xee28d8b544…a8bd37
Audit this contract →
← previous block
·
next block →
recent activity