pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,036,610
← previous block
next block →
recent activity
Analyzing
Block #76,036,610
10 transactions · 8 stateful · 2026-05-21 11:33:33 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,036,610
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execute
· blocks 1
#4
0x5bf9264c
· blocks 1
#6
0x62be7533
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#3
execute
#5
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xc3991994…b9d8
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x0fc41e7b…6831
0x98dc6e…8633
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:
Uniswap: PoolManager
1 conflict on slot
0x330184318b…418f5c
Audit this contract →
← previous block
·
next block →
recent activity