pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,730,033
← previous block
next block →
recent activity
Analyzing
Block #75,730,033
8 transactions · 7 stateful · 2026-05-20 01:30:46 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,730,033
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
removeLiquidity
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x6a0d0f3e
#2
execute
· blocks 1
#3
execute
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
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
0x93f14a12…3309
0x065c9d…c394
2 touches
0 conflicts
0x10c0f1ff…a3f5
0x111111…db61
2 touches
0 conflicts
0x9835db2a…294b
0x111111…db61
2 touches
0 conflicts
0xcb78f92f…9d79
0x111111…db61
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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