pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,948,494
← previous block
next block →
recent activity
Analyzing
Block #75,948,494
9 transactions · 8 stateful · 2026-05-21 01:46:52 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,948,494
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execute
· blocks 2
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
setData
#8
0x39435dac
#3
execute
· blocks 1
#4
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
0x33cb131b…4662
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x75e7d574…6a14
0x065c9d…c394
2 touches
0 conflicts
0x88ccea2c…dae7
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:
USDC (USDC)
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity