pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,110,064
← previous block
next block →
recent activity
Analyzing
Block #85,110,064
10 transactions · 9 stateful · 2026-07-02 12:14:45 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,110,064
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x6a4656ac
#5
0x0f6795d9
· blocks 2
#6
0x6a4656ac
#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
5
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30fa662a…06e0
0x34b655…2a6f
6 touches
3 conflicts
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x45a5887d…8dd7
0x34b655…2a6f
4 touches
1 conflict
0x3c7478b4…cb66
0x34b655…2a6f
2 touches
0 conflicts
0x6db97e95…8353
0x34b655…2a6f
2 touches
0 conflicts
0x6f7a92ed…5651
0x34b655…2a6f
2 touches
0 conflicts
0x84d74093…7808
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
3 conflicts on slot
0x30fa662a9f…0906e0
Audit this contract →
← previous block
·
next block →
recent activity