pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,990,532
← previous block
next block →
recent activity
Analyzing
Block #85,990,532
7 transactions · 6 stateful · 2026-07-06 14:01:18 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.43
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,990,532
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 2
#5
setData
#4
execFwdPositionOps
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd90a674b…29f7
0x34b655…2a6f
6 touches
3 conflicts
0x754c7f04…5673
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64dc
0x34b655…2a6f
4 touches
1 conflict
0x24371e79…270f
0x34b655…2a6f
4 touches
1 conflict
0x07f20d0a…ce83
0x34b655…2a6f
2 touches
0 conflicts
0x1a4d8b60…fc70
0x34b655…2a6f
2 touches
0 conflicts
0x2c506459…5351
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
0xd90a674bde…9a29f7
Audit this contract →
← previous block
·
next block →
recent activity