pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,502,700
← previous block
next block →
recent activity
Analyzing
Block #85,502,700
11 transactions · 11 stateful · 2026-07-04 07:50:27 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,502,700
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
updatePrices
#5
0x0f6795d9
· blocks 1
#7
0xd65e8ff4
#8
0x6a48bbbb
#9
setData
#10
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x16542aa1…9af8
0x065c9d…c394
2 touches
0 conflicts
0x361c73c7…b06f
0x065c9d…c394
2 touches
0 conflicts
0x5603c879…da6c
0x065c9d…c394
2 touches
0 conflicts
0xebe66ccf…8357
0x065c9d…c394
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
0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block
·
next block →
recent activity