pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,360,587
← previous block
next block →
recent activity
Analyzing
Block #86,360,587
12 transactions · 10 stateful · 2026-07-08 07:11:59 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,360,587
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x6a4df8b7
#3
updatePrices
#4
0x3f5c179b
· blocks 1
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x9a622e…e99b
#11
execOrders
#5
0xed82b078
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0x1a3ca58e…6490
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x944c1723…52dd
0x065c9d…c394
3 touches
1 conflict
0x1571866b…aeeb
0x065c9d…c394
3 touches
1 conflict
0x0b5df9ec…6728
0x065c9d…c394
2 touches
0 conflicts
0x27a04273…27c5
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
0x18cf3003ed…9951d1
Audit this contract →
← previous block
·
next block →
recent activity