pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#85,169,356
← previous block
next block →
recent activity
Analyzing
Block #85,169,356
11 transactions · 10 stateful · 2026-07-02 18:50:24 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,169,356
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x5bf9264c
#4
0x5a5d9a99
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#7
0xd10227eb
#8
0x5339c59f
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d7176…6f5e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x04b99a63…7815
0x34b655…2a6f
2 touches
0 conflicts
0x16b3a441…13db
0x34b655…2a6f
2 touches
0 conflicts
0x53c922c1…1f78
0x34b655…2a6f
2 touches
0 conflicts
0x7c0bdc54…9dde
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
0xec1d7176e6…a86f5e
Audit this contract →
← previous block
·
next block →
recent activity