pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,729,142
← previous block
next block →
recent activity
Analyzing
Block #75,729,142
10 transactions · 8 stateful · 2026-05-20 01:24:51 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,729,142
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
· blocks 2
#3
0x5bf9264c
#4
0x5bf9264c
#5
0x0f6795d9
#6
0x0f6795d9
#8
updateDataFeedsValuesPartial
#9
setData
#2
execute
· blocks 1
#7
modifyLiquidities
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
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…8f5d
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5e
0x188d58…ea8e
2 touches
0 conflicts
0x4ea5474b…27d4
0x188d58…ea8e
2 touches
0 conflicts
0x0a3cb2fb…2a14
0x34b655…2a6f
2 touches
0 conflicts
0x0a809ce1…7894
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)
3 conflicts on slot
0x17606ba612…ea1b6e
Audit this contract →
← previous block
·
next block →
recent activity