pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,524,464
← previous block
next block →
recent activity
Analyzing
Block #85,524,464
16 transactions · 15 stateful · 2026-07-04 10:15:17 UTC
Parallelism
88
/100
Blocked
7
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,524,464
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a48ddad
#2
0xcf7468f4
#3
execute
#4
exactInputSingle
#5
exactInputSingle
#6
0xab083028
#7
updatePrices
· blocks 1
#9
0x5a5d9a99
#10
0x0f6795d9
#11
executeBatch
#12
0x0c7abd22
#13
updateDataFeedsValuesPartial
#14
setData
#15
0x39435dac
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x6af306bb…2e81
0x3bd359…433a
2 touches
0 conflicts
0xce8bbe33…b72e
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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:
0x04fdeac2…f747d7
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity