pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,579,807
← previous block
next block →
recent activity
Analyzing
Block #85,579,807
10 transactions · 9 stateful · 2026-07-04 16:23:49 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,579,807
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
collectFees
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
#5
0xec2bd3f2
#6
0x6a49340d
#7
setData
#8
0x39435dac
· blocks 1
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0x6cb73699…4b81
0x34b655…2a6f
4 touches
1 conflict
0x33e3dcdd…1f1f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x06d2a0e6…2154
0x34b655…2a6f
2 touches
0 conflicts
0x1f356c5d…bf12
0x34b655…2a6f
2 touches
0 conflicts
0x2382a4de…a921
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
0x11431f9df7…2942c5
Audit this contract →
← previous block
·
next block →
recent activity