pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,913,340
← previous block
next block →
recent activity
Analyzing
Block #85,913,340
11 transactions · 8 stateful · 2026-07-06 05:26:13 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,913,340
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
setData
#7
0x438654…48d5
#8
0xa7a6ea…b909
#9
execOrders
· blocks 1
#10
execOrders
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
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0x31152b1f…e76a
0x34b655…2a6f
4 touches
1 conflict
0x26fda8d3…d5b4
0x34b655…2a6f
2 touches
0 conflicts
0x547feec8…29b6
0x34b655…2a6f
2 touches
0 conflicts
0x79e45bd8…5d05
0x34b655…2a6f
2 touches
0 conflicts
0xafd867b7…2b2d
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
0x8fbde2b3d3…899b8f
Audit this contract →
← previous block
·
next block →
recent activity