pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,138,696
← previous block
next block →
recent activity
Analyzing
Block #80,138,696
10 transactions · 8 stateful · 2026-06-09 11:33:15 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,138,696
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x0f6795d9
#3
0x0f6795d9
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x6a27fa73
#7
transfer
· blocks 1
#9
setData
#8
transfer
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
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0bb40033…8b11
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x42deaa13…f045
0x34b655…2a6f
2 touches
0 conflicts
0x56c55026…fd69
0x34b655…2a6f
2 touches
0 conflicts
0x66b4cd65…9b29
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:
USDC (USDC)
1 conflict on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity