pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,962,691
← previous block
next block →
recent activity
Analyzing
Block #94,962,691
11 transactions · 9 stateful · 2026-08-11 04:11:19 UTC
Parallelism
82
/100
Blocked
33
%
Avg conflicts / tx
0.27
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,962,691
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5acec890
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
placeAndExecuteMarketSell
· blocks 2
#9
updateDataFeedsValuesPartial
#10
setData
#6
placeAndExecuteMarketSell
#7
0x3f5c179b
#8
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xc22742f5…ee0a
0x065c9d…c394
3 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
2 touches
0 conflicts
0x4f1e16d4…4833
0x34b655…2a6f
2 touches
0 conflicts
0x59bfb0ed…ebd2
0x34b655…2a6f
2 touches
0 conflicts
0x8493ba99…3412
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity