pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,165,852
← previous block
next block →
recent activity
Analyzing
Block #86,165,852
14 transactions · 13 stateful · 2026-07-07 09:31:38 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,165,852
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPrice
#3
setPrice
#4
setPrice
#5
approve
#6
0x39435dac
· blocks 1
#7
updateDataFeedsValuesPartial
#8
removeLiquidityNATIVE
#9
setData
#10
0x0f6795d9
#11
0x5339c59f
#12
0x0f6795d9
#13
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x2b5aa7ed…b3db
0x34b655…2a6f
2 touches
0 conflicts
0x76409f96…0ca6
0x34b655…2a6f
2 touches
0 conflicts
0xa15a23ec…fc69
0x34b655…2a6f
2 touches
0 conflicts
0xde398ff4…00ca
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:
Perpl
1 conflict on slot
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity