pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,852,667
← previous block
next block →
recent activity
Analyzing
Block #100,852,667
9 transactions · 8 stateful · 2026-08-31 20:35:06 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,852,667
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x59558d29
#2
execOrders
#3
execOrders
#4
placeAndExecuteMarketSell
· blocks 2
#7
execFwdPositionOpsV2
#8
setData
#5
placeAndExecuteMarketSell
· blocks 1
#6
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x6518075e…2b17
0x2a68ba…90c5
6 touches
3 conflicts
0xd6ab7de7…5804
0x40c49f…2af0
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
2 touches
0 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
2 touches
0 conflicts
0x73a0005f…70a8
0x34b655…2a6f
2 touches
0 conflicts
0x7ce74eed…3383
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
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity