pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,823,912
← previous block
next block →
recent activity
Analyzing
Block #85,823,912
13 transactions · 10 stateful · 2026-07-05 19:30:30 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,823,912
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#2
exactOutputSingle
#3
updatePrices
#5
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x48c6a4…7dff
#10
0x488c21…8f6c
#11
execOrders
#12
0xc7e3ec2c
#4
0x0c7abd22
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9292abf8…d65c
0x065c9d…c394
3 touches
1 conflict
0xf6cbf57f…987a
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0xd519f276…aa62
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0002
0x094452…0a09
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
0x9292abf8b7…86d65c
Audit this contract →
← previous block
·
next block →
recent activity