pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,774,712
← previous block
next block →
recent activity
Analyzing
Block #84,774,712
14 transactions · 13 stateful · 2026-06-30 22:56:53 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,774,712
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
setPrice
#2
setPrice
#3
setPrice
#4
setPriceForArbitrum
#5
setPrice
#6
setPrice
#7
0xab083028
#8
updateDataFeedsValuesPartial
#9
updatePrices
#10
0x5a5d9a99
· blocks 1
#11
setData
#13
0x6a444a2d
#12
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe408054…d52a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xb6226823…c2e1
0x3c2269…cf62
2 touches
0 conflicts
0x2f6e3f9b…cced
0x3c2269…cf62
2 touches
0 conflicts
0x045a6f92…2492
0x3c2269…cf62
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
0xbe40805443…51d52a
Audit this contract →
← previous block
·
next block →
recent activity