pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,383,643
← previous block
next block →
recent activity
Analyzing
Block #76,383,643
8 transactions · 7 stateful · 2026-05-23 02:05:40 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,383,643
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
updatePrices
#4
0x2f571677
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#5
0x2f571677
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06956408…967b
0x754704…b603
4 touches
1 conflict
0x33f502ea…f39a
0x754704…b603
4 touches
1 conflict
0xfd4bd0e6…5918
0x754704…b603
4 touches
1 conflict
0xc39192d6…d4df
0xae0830…85fe
4 touches
1 conflict
0x2b936aa5…05e0
0xe0b5d2…9231
4 touches
1 conflict
0x2b936aa5…05e1
0xe0b5d2…9231
4 touches
1 conflict
0xfc8da555…56e8
0xae0830…85fe
3 touches
1 conflict
0xf63613c1…4939
0xae0830…85fe
3 touches
1 conflict
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
0x06956408a4…25967b
Audit this contract →
← previous block
·
next block →
recent activity