pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,912,058
← previous block
next block →
recent activity
Analyzing
Block #85,912,058
13 transactions · 9 stateful · 2026-07-06 05:17:40 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,912,058
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
withdraw
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x6a4b3aec
#9
setData
#10
0x3e6334…b5d2
#11
exactInputSingle
#12
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0x45ef6fad…5e43
0x34b655…2a6f
3 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x0eeb2a30…6909
0x34b655…2a6f
2 touches
0 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
2 touches
0 conflicts
0x2f358e74…1022
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
0xe06bbb2ef5…889416
Audit this contract →
← previous block
·
next block →
recent activity