pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,178,547
← previous block
next block →
recent activity
Analyzing
Block #75,178,547
10 transactions · 7 stateful · 2026-05-17 12:00:09 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,178,547
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#3
exactInputSingle
#4
updateDataFeedsValuesPartial
#5
0xa54c4faf
#6
setData
#7
0x3bc479…5f5d
#8
0x4d71eb…b23a
#9
delegate
#2
0x1ffa3c9b
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
0xfb8e63d0…4b29
0x065c9d…c394
3 touches
1 conflict
0xd420689a…f7f1
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2286c732…f1d1
0x065c9d…c394
2 touches
0 conflicts
0x3ff14f32…8377
0x065c9d…c394
2 touches
0 conflicts
0x9206c78d…8519
0x065c9d…c394
2 touches
0 conflicts
0xa22714a5…db90
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xfb8e63d0bc…794b29
Audit this contract →
← previous block
·
next block →
recent activity