pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,875,448
← previous block
next block →
recent activity
Analyzing
Block #85,875,448
10 transactions · 10 stateful · 2026-07-06 01:13:47 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,875,448
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
_makeSwaps
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
poke
#6
0x0f6795d9
· blocks 1
#8
setData
#9
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xb96c408d…7113
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
2 touches
0 conflicts
0x78eb0de5…1db2
0x01bff4…1071
2 touches
0 conflicts
0xc00fc7fc…f47e
0x01bff4…1071
2 touches
0 conflicts
0x0fde64da…aa3e
0x2a68ba…90c5
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
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
0x8e5cc69035…0db06b
Audit this contract →
← previous block
·
next block →
recent activity