pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,083,008
← previous block
next block →
recent activity
Analyzing
Block #99,083,008
14 transactions · 8 stateful · 2026-08-25 15:50:45 UTC
Parallelism
86
/100
Blocked
13
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,083,008
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execOrders
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#7
placeAndExecuteMarketSell
#8
placeAndExecuteMarketBuy
#9
placeAndExecuteMarketSell
#10
placeAndExecuteMarketBuy
#11
0x3f5c179b
#12
bet
#13
setData
#2
0x0c7abd22
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
0x42288d1e…38f1
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1ce1f393…6039
0x065c9d…c394
2 touches
0 conflicts
0x40ecd90c…10ed
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x7a8e4931…bb03
0x065c9d…c394
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0x42288d1ee0…8738f1
Audit this contract →
← previous block
·
next block →
recent activity