pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,568,464
← previous block
next block →
recent activity
Analyzing
Block #95,568,464
9 transactions · 8 stateful · 2026-08-13 07:12:41 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,568,464
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
bet
#6
execFwdPositionOps
#7
0x6a7d6ee1
#8
setData
#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
0xdc255d21…c377
0x754704…b603
4 touches
1 conflict
0xa949d556…184c
0x754704…b603
4 touches
1 conflict
0xaad1c5c0…ab91
0x754704…b603
4 touches
1 conflict
0x48f7aa8f…39c8
0x8f415d…5241
2 touches
0 conflicts
0x4dbb0f3e…2028
0x99c7a7…8bf0
2 touches
0 conflicts
0x8ee86cb5…db9c
0x99c7a7…8bf0
2 touches
0 conflicts
0x9bbb26e8…0d2e
0x99c7a7…8bf0
2 touches
0 conflicts
0xef712f4a…0853
0x99c7a7…8bf0
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
0xdc255d2170…b4c377
Audit this contract →
← previous block
·
next block →
recent activity