pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,065,722
← previous block
next block →
recent activity
Analyzing
Block #94,065,722
11 transactions · 9 stateful · 2026-08-08 00:42:25 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,065,722
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
deposit
#3
updatePrices
#4
placeAndExecuteMarketBuy
· blocks 1
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x32366535
#10
0xc7e3ec2c
#5
placeAndExecuteMarketBuy
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41d8fbd…2858
0xa6afd3…d132
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2cb503ef…7eb3
0x0c65a0…0852
2 touches
0 conflicts
0x52c63247…ce02
0x0c65a0…0852
2 touches
0 conflicts
0x019e122e…75b3
0x34b655…2a6f
2 touches
0 conflicts
0x039f1f6c…3155
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-WETH/USDC
1 conflict on slot
0xd41d8fbdd1…da2858
Audit this contract →
← previous block
·
next block →
recent activity