pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,190,391
← previous block
next block →
recent activity
Analyzing
Block #74,190,391
10 transactions · 8 stateful · 2026-05-12 22:04:26 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,190,391
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#4
updateDataFeedsValuesPartial
#5
0xd10227eb
#6
0x39435dac
#7
execute
#8
setData
#9
0x6a03a462
#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
0x2c1b93c2…60b5
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
0x279a8801…cc6d
0x065c9d…c394
2 touches
0 conflicts
0x40657f82…8241
0x065c9d…c394
2 touches
0 conflicts
0xe50e8dd5…713c
0x065c9d…c394
2 touches
0 conflicts
0xf823e97f…2ee6
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
0x2c1b93c2fb…c760b5
Audit this contract →
← previous block
·
next block →
recent activity