pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,271,635
← previous block
next block →
recent activity
Analyzing
Block #86,271,635
13 transactions · 12 stateful · 2026-07-07 21:18:00 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,271,635
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execOrders
#3
forward
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x1a945f9c
#7
executeBatch
#8
0x3f5c179b
#9
0xed82b078
· blocks 1
#11
setData
#12
execOrders
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
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
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x2b4e1915…8a3a
0x1efe02…37d6
2 touches
0 conflicts
0x35bf4566…a51f
0x1efe02…37d6
2 touches
0 conflicts
0x04f6d949…d859
0x34b655…2a6f
2 touches
0 conflicts
0x55803256…09e9
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
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-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity