pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,032,583
← previous block
next block →
recent activity
Analyzing
Block #75,032,583
10 transactions · 7 stateful · 2026-05-16 19:46:03 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,032,583
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#4
updateDataFeedsValuesPartial
#5
0x98717539
#6
0x5339c59f
#7
0x5339c59f
#8
0x6a08c9f3
#9
setData
#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
0xe2020649…5cf2
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
0x3ff2589f…7641
0x065c9d…c394
2 touches
0 conflicts
0x4dfcc0c9…2a4e
0x065c9d…c394
2 touches
0 conflicts
0x72b99fc8…eb11
0x065c9d…c394
2 touches
0 conflicts
0xae83f89c…d9ad
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
0xe2020649e0…705cf2
Audit this contract →
← previous block
·
next block →
recent activity