pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,898,077
← previous block
next block →
recent activity
Analyzing
Block #85,898,077
13 transactions · 11 stateful · 2026-07-06 03:44:34 UTC
Parallelism
77
/100
Blocked
18
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,898,077
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
forward
#6
0xed82b078
#7
execFwdPositionOps
#8
transfer
#9
setData
#10
execOrders
· blocks 2
#11
execOrders
· blocks 1
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa51de3df…c65a
0x34b655…2a6f
4 touches
1 conflict
0xcc25f1e5…2cac
0x34b655…2a6f
4 touches
1 conflict
0xccbd06e4…ec7c
0x34b655…2a6f
4 touches
1 conflict
0x134d9128…baac
0x34b655…2a6f
4 touches
1 conflict
0x63c900f4…2600
0x34b655…2a6f
4 touches
1 conflict
0x34dfc3bc…33de
0x34b655…2a6f
2 touches
0 conflicts
0x55d08ae4…42ec
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
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity