pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,159,538
← previous block
next block →
recent activity
Analyzing
Block #85,159,538
10 transactions · 9 stateful · 2026-07-02 17:45:05 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,159,538
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidityNATIVE
#2
0x7c51d6cf
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#6
0x0f6795d9
#7
0x0f6795d9
#8
setData
#9
0x39435dac
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ec06b18…2e5a
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0f3050b5…c2d3
0x34b655…2a6f
2 touches
0 conflicts
0x13a3bd59…8bab
0x34b655…2a6f
2 touches
0 conflicts
0x27c5f398…4c1e
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
0x6ec06b1870…832e5a
Audit this contract →
← previous block
·
next block →
recent activity