pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,195,465
← previous block
next block →
recent activity
Analyzing
Block #75,195,465
9 transactions · 8 stateful · 2026-05-17 13:53:01 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,195,465
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#3
exactInputSingle
#5
updateDataFeedsValuesPartial
#6
exactInputSingle
#7
setData
#8
0x39435dac
#2
0x1ffa3c9b
· blocks 1
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d7a307…4d63
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3e23b56f…bb78
0x065c9d…c394
2 touches
0 conflicts
0xae83f89c…d9ad
0x065c9d…c394
2 touches
0 conflicts
0xc245e23f…4fe6
0x065c9d…c394
2 touches
0 conflicts
0xf9f04ff1…3e0f
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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:
Kuru Exchange: Market-MON/USDC
3 conflicts on slot
0xf3d7a307cc…f14d63
Audit this contract →
← previous block
·
next block →
recent activity