pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,485,247
← previous block
next block →
recent activity
Analyzing
Block #83,485,247
10 transactions · 10 stateful · 2026-06-24 23:40:34 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,485,247
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x5a5d9a99
#4
handleOps
· blocks 2
#7
execFwdPositionOps
#8
setData
#9
execOrders
#5
handleOps
· blocks 1
#6
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x754704…b603
6 touches
3 conflicts
0x34b1e500…7687
0x754704…b603
6 touches
3 conflicts
0xd0fdd34f…60c2
0x754704…b603
6 touches
3 conflicts
0xee70c256…3665
0x754704…b603
6 touches
3 conflicts
0x00000000…000b
0x78999c…f371
6 touches
3 conflicts
0x00000000…000f
0x78999c…f371
6 touches
3 conflicts
0xe0659a3f…90d9
0x000000…a032
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
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:
USDC (USDC)
3 conflicts on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity