pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#82,521,822
← previous block
next block →
recent activity
Analyzing
Block #82,521,822
15 transactions · 12 stateful · 2026-06-20 12:20:30 UTC
Parallelism
80
/100
Blocked
17
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#82,521,822
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1bc6d9…7620
#2
0x5339c59f
#3
0xab083028
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x6a368606
#8
swapExactTokenForPt
#9
0x5a5d9a99
#10
0x5a5d9a99
#11
forward
#12
transfer
· blocks 2
#13
transfer
· blocks 1
#14
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
12
w0
13
w1
14
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xdafb5114…1aa1
0x000000…4321
2 touches
0 conflicts
0x09973e19…f252
0x000000…012a
2 touches
0 conflicts
0x11d9469d…fa7e
0x000000…012a
2 touches
0 conflicts
0x5302aee9…1d28
0x000000…012a
2 touches
0 conflicts
0x886d4df6…1655
0x000000…012a
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:
USDC (USDC)
3 conflicts on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity