pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,104,261
← previous block
next block →
recent activity
Analyzing
Block #85,104,261
13 transactions · 10 stateful · 2026-07-02 11:35:57 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,104,261
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
0x5a5d9a99
#4
deposit
#6
updateDataFeedsValuesPartial
#7
0x6a464d95
#8
0xb6fa15…87c6
#9
0xbb7ef6…0750
#10
setData
#11
0x39435dac
#12
0xc7e3ec2c
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x11b2f926…7393
0x065c9d…c394
2 touches
0 conflicts
0x5bb88c5d…4e65
0x065c9d…c394
2 touches
0 conflicts
0xd40cd174…05f9
0x065c9d…c394
2 touches
0 conflicts
0xf6964401…7bac
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity