pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,412,628
← previous block
next block →
recent activity
Analyzing
Block #85,412,628
11 transactions · 10 stateful · 2026-07-03 21:50:46 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,412,628
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x5a5d9a99
#6
0x0f6795d9
#8
0x6a482f2d
#9
setData
#10
0xc7e3ec2c
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6789fdc1…ff11
0x065c9d…c394
4 touches
1 conflict
0x9b55ff70…01a2
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7fef6798…c2fc
0x065c9d…c394
3 touches
1 conflict
0xe8302a61…4daa
0x065c9d…c394
3 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
2 touches
0 conflicts
0x45f562b2…9294
0x69df8a…6292
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
0x6789fdc1ea…b5ff11
Audit this contract →
← previous block
·
next block →
recent activity