pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,656,089
← previous block
next block →
recent activity
Analyzing
Block #85,656,089
10 transactions · 10 stateful · 2026-07-05 00:51:44 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,656,089
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a49ab17
#2
execute
#3
0x6ad2e98b
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updatePrices
#8
forward
#9
setData
#4
0xab083028
· blocks 1
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc379dcd…c131
0x065c9d…c394
4 touches
1 conflict
0x4cb3f181…31aa
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdeb7d3df…1c38
0x065c9d…c394
3 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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
0xbc379dcdce…9cc131
Audit this contract →
← previous block
·
next block →
recent activity