pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,099,515
← previous block
next block →
recent activity
Analyzing
Block #75,099,515
10 transactions · 8 stateful · 2026-05-17 03:12:30 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,099,515
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
removeLiquidity
#2
0x6a093296
#3
0x6a093296
#4
0x1ffa3c9b
· blocks 1
#5
0x98717539
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#6
0x98717539
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e530544…82db
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8d2c4dea…5e0b
0x065c9d…c394
3 touches
1 conflict
0x47287f4e…71c4
0x065c9d…c394
3 touches
1 conflict
0x91695e36…9b08
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
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:
0x065c9d28…a9c394
1 conflict on slot
0x7e53054403…5882db
Audit this contract →
← previous block
·
next block →
recent activity