pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,949,174
← previous block
next block →
recent activity
Analyzing
Block #85,949,174
9 transactions · 7 stateful · 2026-07-06 09:25:17 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,949,174
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
0x6a4b74f5
#6
setData
#7
0x4ea88f…d83f
#8
0x39435dac
#3
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39cc2185…cacb
0x34b655…2a6f
4 touches
1 conflict
0x94b1f3d6…f85c
0x34b655…2a6f
4 touches
1 conflict
0x39cc2185…caca
0x34b655…2a6f
4 touches
1 conflict
0xe1a43e09…8935
0x34b655…2a6f
3 touches
1 conflict
0x59e4ffbf…f01b
0x34b655…2a6f
2 touches
0 conflicts
0x781f1ffa…2ab7
0x34b655…2a6f
2 touches
0 conflicts
0x79b3209b…f766
0x34b655…2a6f
2 touches
0 conflicts
0x7aad02c6…b979
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
0x39cc218566…27cacb
Audit this contract →
← previous block
·
next block →
recent activity