pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,789,110
← previous block
next block →
recent activity
Analyzing
Block #75,789,110
12 transactions · 8 stateful · 2026-05-20 08:03:44 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,789,110
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#4
0xab083028
#5
0x5bf9264c
#6
0x5bf9264c
#7
execute
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x811299…4822
#11
0xeb351c…69fc
#2
0x0c7abd22
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
0xcd819349…9480
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x37801694…9efc
0x065c9d…c394
2 touches
0 conflicts
0x4a5608c8…ed72
0x065c9d…c394
2 touches
0 conflicts
0x54b8164b…d2f0
0x065c9d…c394
2 touches
0 conflicts
0xa1957c47…48b0
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0xcd81934985…f09480
Audit this contract →
← previous block
·
next block →
recent activity