pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,703,479
← previous block
next block →
recent activity
Analyzing
Block #85,703,479
11 transactions · 10 stateful · 2026-07-05 06:08:36 UTC
Parallelism
64
/100
Blocked
30
%
Avg conflicts / tx
0.36
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,703,479
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0xab083028
· blocks 2
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
setData
#8
execOrders
#9
execFwdPositionOps
#10
execOrders
#2
0x6ad2e98b
· blocks 1
#3
0xab083028
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x34401412…4cdc
0x40c49f…2af0
2 touches
0 conflicts
0x45045cd1…af6e
0x40c49f…2af0
2 touches
0 conflicts
0x8211881b…20a8
0x40c49f…2af0
2 touches
0 conflicts
0xb88785d1…2309
0x40c49f…2af0
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: MarginAccount
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity