pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,502,074
← previous block
next block →
recent activity
Analyzing
Block #85,502,074
10 transactions · 8 stateful · 2026-07-04 07:46:17 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,502,074
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 2
#4
metacall
#5
0x3f5c179b
#8
0x6a48bac1
#9
setData
#6
0x0f6795d9
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x326a02b5…8dad
0x34b655…2a6f
2 touches
0 conflicts
0x3a8f2d47…590a
0x34b655…2a6f
2 touches
0 conflicts
0x503b3a72…f6df
0x34b655…2a6f
2 touches
0 conflicts
0x548145a9…cfce
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
0xafd867b7ed…d92b2e
Audit this contract →
← previous block
·
next block →
recent activity