pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,770,318
← previous block
next block →
recent activity
Analyzing
Block #85,770,318
12 transactions · 6 stateful · 2026-07-05 13:33:35 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,770,318
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0xed82b078
· blocks 1
#5
setData
#6
0x3c33d3…8e4f
#7
0xd714f8…fd77
#8
0xb20bf2…a80d
#9
0xd24a10…d034
#10
execOrders
#11
execOrders
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x5541184b…40c0
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0x77991f1a…56d5
0x065c9d…c394
2 touches
0 conflicts
0xf500369c…9f32
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity