pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,806,809
← previous block
next block →
recent activity
Analyzing
Block #85,806,809
13 transactions · 12 stateful · 2026-07-05 17:36:43 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,806,809
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPriceForArbitrum
#3
setPrice
#4
setPrice
#5
setPrice
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
· blocks 1
#8
forward
#9
0x3f5c179b
#11
0x6a4a96a2
#12
setData
#10
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9a92b6a…01dc
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x73c70c38…41a3
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x396d1454…e247
0x34b655…2a6f
2 touches
0 conflicts
0x4a11a172…dbef
0x34b655…2a6f
2 touches
0 conflicts
0x4f7cccfa…38d5
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
0xd9a92b6a14…1901dc
Audit this contract →
← previous block
·
next block →
recent activity