pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,019,268
← previous block
next block →
recent activity
Analyzing
Block #82,019,268
13 transactions · 11 stateful · 2026-06-18 04:28:28 UTC
Parallelism
69
/100
Blocked
27
%
Avg conflicts / tx
0.46
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,019,268
· 13 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
exactInputSingle
#4
0x3f5c179b
#5
execute
· blocks 3
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
0x6a337464
#12
setData
#6
execute
· blocks 2
#7
execute
· blocks 1
#8
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0xa4e3b3b1…0911
0x2a68ba…90c5
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x7cfdc4…1fbd
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:
0x788571e0…f48888
6 conflicts on slot
0x797464dbf4…70e15a
Audit this contract →
← previous block
·
next block →
recent activity