pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,606,009
← previous block
next block →
recent activity
Analyzing
Block #84,606,009
14 transactions · 11 stateful · 2026-06-30 04:12:59 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,606,009
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc1274a2e
#2
0xab083028
#3
updatePrices
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x62be7533
#8
forward
#9
updateDataFeedsValuesPartial
#10
0x5b5877d3
#11
0x6a4342c3
#12
setData
#13
0x50a0b275
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x6dc6f2d0…9ac4
0x065c9d…c394
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x9fc8b97d…96da
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:
0xd637b38f…c64160
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity