pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#75,990,327
← previous block
next block →
recent activity
Analyzing
Block #75,990,327
11 transactions · 9 stateful · 2026-05-21 06:25:27 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,990,327
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#3
transfer
#4
0xab083028
#5
0x98717539
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
exactInputSingle
#10
setData
#2
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x3e61c93f…f2af
0x065c9d…c394
2 touches
0 conflicts
0x5a1553e2…e9ea
0x065c9d…c394
2 touches
0 conflicts
0x5e4d55e3…713c
0x065c9d…c394
2 touches
0 conflicts
0x797bdc6a…8ed3
0x065c9d…c394
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…418f5d
Audit this contract →
← previous block
·
next block →
recent activity