pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,562,240
← previous block
next block →
recent activity
Analyzing
Block #74,562,240
13 transactions · 9 stateful · 2026-05-14 15:24:00 UTC
Parallelism
77
/100
Blocked
22
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,562,240
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1ffa3c9b
· blocks 2
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
#9
0x6a05e988
#10
setData
#11
0x39435dac
#12
0x39435dac
#7
0xed82b078
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x96840480…1165
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x8640a8c8…cdd0
0x065c9d…c394
3 touches
1 conflict
0x1224f6be…8b53
0x065c9d…c394
2 touches
0 conflicts
0x42a7f118…5554
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
2 touches
0 conflicts
0x765c236f…ff45
0x2a68ba…90c5
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity