pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,458,688
← previous block
next block →
recent activity
Analyzing
Block #85,458,688
10 transactions · 8 stateful · 2026-07-04 02:57:28 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,458,688
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x4d8dc985
#3
updateDataFeedsValuesPartial
#4
0x6a487710
#5
0x0c7abd22
#6
0x6a487710
#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
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x1bee5aea…5f61
0x34b655…2a6f
4 touches
1 conflict
0x2fa4ab82…4b34
0x34b655…2a6f
4 touches
1 conflict
0x517d35c7…f359
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0x7e4b5149…c444
0x34b655…2a6f
4 touches
1 conflict
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
0xe732567db9…26b65d
Audit this contract →
← previous block
·
next block →
recent activity