pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,245,936
← previous block
next block →
recent activity
Analyzing
Block #86,245,936
15 transactions · 12 stateful · 2026-07-07 18:26:27 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,245,936
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
execOrders
#4
execOrders
#5
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
0x6a4d454b
#9
setData
#10
redeemDelegations
#11
execOrders
#12
execOrders
#13
jMMeC
#14
0xc7e3ec2c
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x4a4dbc44…a34c
0x065c9d…c394
2 touches
0 conflicts
0x86be5bcf…a404
0x065c9d…c394
2 touches
0 conflicts
0x998fe05a…937b
0x065c9d…c394
2 touches
0 conflicts
0xe0e80128…cdc9
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
0xcc4f1f1446…7caa5f
Audit this contract →
← previous block
·
next block →
recent activity