pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,924,972
← previous block
next block →
recent activity
Analyzing
Block #100,924,972
10 transactions · 10 stateful · 2026-09-01 02:38:48 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,924,972
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
#2
execOrders
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
placeAndExecuteMarketBuy
· blocks 1
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#6
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2cdf2f20…b596
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x1af899ef…9615
0x34b655…2a6f
2 touches
0 conflicts
0x22badbc6…4c24
0x34b655…2a6f
2 touches
0 conflicts
0x26253352…1a75
0x34b655…2a6f
2 touches
0 conflicts
0x33649c4f…b327
0x34b655…2a6f
2 touches
0 conflicts
0x9d6a99f9…da64
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x2cdf2f2086…80b596
Audit this contract →
← previous block
·
next block →
recent activity