pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,837,831
← previous block
next block →
recent activity
Analyzing
Block #85,837,831
11 transactions · 10 stateful · 2026-07-05 21:03:12 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,837,831
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
supply
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
addLiquidityNATIVE
#6
0x0f6795d9
#7
0x6a4ac708
#8
setData
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x5624e473…1e16
0x34b655…2a6f
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d6
0x69a5f9…2fef
2 touches
0 conflicts
0xaf831072…51d7
0x69a5f9…2fef
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
0x6637e421bf…b0af93
Audit this contract →
← previous block
·
next block →
recent activity