pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,457,738
← previous block
next block →
recent activity
Analyzing
Block #84,457,738
11 transactions · 10 stateful · 2026-06-29 11:43:40 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,457,738
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
execFwdPositionOps
#5
0xed82b078
· blocks 1
#7
setData
#8
execOrders
#9
0x50a0b275
#10
0xc7e3ec2c
#6
0xed82b078
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
0x7b7af531…48f1
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b6e8fc2…73d4
0x34b655…2a6f
2 touches
0 conflicts
0x1faf8189…bd1d
0x34b655…2a6f
2 touches
0 conflicts
0x242bdfb5…974d
0x34b655…2a6f
2 touches
0 conflicts
0x36388e0c…7067
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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
0x7b7af53137…5748f1
Audit this contract →
← previous block
·
next block →
recent activity