pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,555,902
← previous block
next block →
recent activity
Analyzing
Block #95,555,902
10 transactions · 10 stateful · 2026-08-13 06:09:31 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
#95,555,902
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
· blocks 2
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
executeBatch
#8
setData
#9
0x59558d29
#2
matchOrders
· blocks 1
#7
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad1c5c0…ab91
0x754704…b603
6 touches
3 conflicts
0xa949d556…184c
0x754704…b603
4 touches
1 conflict
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0x8ee86cb5…db9c
0x99c7a7…8bf0
4 touches
1 conflict
0x9bbb26e8…0d2e
0x99c7a7…8bf0
4 touches
1 conflict
0x25ef5065…186a
0x8f415d…5241
3 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
2 touches
0 conflicts
0xcb165620…1189
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)
3 conflicts on slot
0xaad1c5c0ee…1fab91
Audit this contract →
← previous block
·
next block →
recent activity