pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,473,817
← previous block
next block →
recent activity
Analyzing
Block #95,473,817
12 transactions · 11 stateful · 2026-08-12 23:16:39 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,473,817
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
postStateList
#4
0x5acec890
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0x6a7cff4f
#10
setData
#11
0x59558d29
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0x4dbb0f3e…2028
0x99c7a7…8bf0
4 touches
1 conflict
0xef712f4a…0853
0x99c7a7…8bf0
4 touches
1 conflict
0xa949d556…184c
0x754704…b603
4 touches
1 conflict
0x51924b00…543e
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
0x34b655…2a6f
2 touches
0 conflicts
0xa041d917…c0a6
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:
USDC (USDC)
1 conflict on slot
0xaad1c5c0ee…1fab91
Audit this contract →
← previous block
·
next block →
recent activity