pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,539,469
← previous block
next block →
recent activity
Analyzing
Block #93,539,469
10 transactions · 9 stateful · 2026-08-06 04:35:59 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,539,469
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execTransaction
#2
placeAndExecuteMarketSell
· blocks 1
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x6a740fa7
#9
setData
#3
placeAndExecuteMarketBuy
· blocks 1
#4
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x6a7556ed…fa4a
0x851145…3f07
3 touches
1 conflict
0xd82f3ce2…5c31
0x01bff4…1071
2 touches
0 conflicts
0xf13704e6…258a
0x01bff4…1071
2 touches
0 conflicts
0x00000000…0005
0x25dafa…4d3d
2 touches
0 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity