pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,165,291
← previous block
next block →
recent activity
Analyzing
Block #86,165,291
13 transactions · 11 stateful · 2026-07-07 09:27:53 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,165,291
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
cancel
#6
0x0f6795d9
#7
batchUpdate
#8
setData
#9
0x785f5745
#10
exactInputSingle
#11
0x39435dac
#12
0xc7e3ec2c
#3
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb245fe36…d765
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
0x157dbfb2…4089
0x34b655…2a6f
2 touches
0 conflicts
0x177d036a…1c5d
0x34b655…2a6f
2 touches
0 conflicts
0x18446f68…c48b
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
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
0xb245fe3647…73d765
Audit this contract →
← previous block
·
next block →
recent activity