pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#84,500,736
← previous block
next block →
recent activity
Analyzing
Block #84,500,736
13 transactions · 10 stateful · 2026-06-29 16:30:36 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,500,736
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x0f6795d9
#8
forward
#9
0x0f6795d9
#10
0x6a429e24
#11
setData
#12
0x39435dac
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aa23381…e172
0x405b63…7777
4 touches
1 conflict
0xa74cd79c…705a
0x405b63…7777
4 touches
1 conflict
0x00000000…0000
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0001
0xaa5de1…d330
4 touches
1 conflict
0x00000000…0003
0xaa5de1…d330
4 touches
1 conflict
0xbcc1b459…f94f
0x3bd359…433a
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
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:
0x405b6330…827777
1 conflict on slot
0x9aa23381c2…d3e172
Audit this contract →
← previous block
·
next block →
recent activity