pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,297,235
← previous block
next block →
recent activity
Analyzing
Block #95,297,235
10 transactions · 9 stateful · 2026-08-12 08:24:06 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,297,235
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
handleOps
· blocks 1
#4
0x0f6795d9
#5
0x0f6795d9
#6
updateTemporalNumericValuesV1
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#3
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x754704…b603
4 touches
1 conflict
0x34b1e500…7687
0x754704…b603
4 touches
1 conflict
0xe0659a3f…90d9
0x000000…a032
4 touches
1 conflict
0x00000000…000b
0x78999c…f371
4 touches
1 conflict
0x00000000…000f
0x78999c…f371
4 touches
1 conflict
0x004989aa…b35a
0x34b655…2a6f
2 touches
0 conflicts
0x5e401f24…5d4e
0x754704…b603
2 touches
0 conflicts
0xaad1c5c0…ab91
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:
USDC (USDC)
1 conflict on slot
0x0000000000…00000b
Audit this contract →
← previous block
·
next block →
recent activity