pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,544,705
← previous block
next block →
recent activity
Analyzing
Block #85,544,705
9 transactions · 8 stateful · 2026-07-04 12:30:03 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,544,705
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
updatePrices
#4
0x0f6795d9
· blocks 1
#5
handleOps
#7
0x6a48fd43
#8
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefcdf197…96a2
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x14a71e9b…8870
0x34b655…2a6f
2 touches
0 conflicts
0x16c6549d…b016
0x34b655…2a6f
2 touches
0 conflicts
0x20fb0b1c…12f3
0x34b655…2a6f
2 touches
0 conflicts
0x30faf03c…78b1
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
0xefcdf19725…1096a2
Audit this contract →
← previous block
·
next block →
recent activity