pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,100,876
← previous block
next block →
recent activity
Analyzing
Block #80,100,876
11 transactions · 7 stateful · 2026-06-09 07:21:29 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,100,876
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6943a490
#2
approve
· blocks 1
#4
0xab083028
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x98717539
#8
setData
#9
0xdaa5d1…6d0e
#10
withdraw
#3
deposit
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
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xdb34e660…fdc0
0x0a4fcb…a602
2 touches
0 conflicts
0xdb34e660…fdc6
0x0a4fcb…a602
2 touches
0 conflicts
0xdb34e660…fdc7
0x0a4fcb…a602
2 touches
0 conflicts
0xdb34e660…fdc8
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
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)
1 conflict on slot
0x487d2922ff…7828b6
Audit this contract →
← previous block
·
next block →
recent activity