pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,730,841
← previous block
next block →
recent activity
Analyzing
Block #74,730,841
9 transactions · 6 stateful · 2026-05-15 10:10:14 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,730,841
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
0x0c7abd22
#2
updatePrices
#3
updateDataFeedsValuesPartial
#5
0x6a06f17e
#6
0x6a06f17e
#7
setData
#8
0x39435dac
#4
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x0b000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1f63e3ea…6b03
0x065c9d…c394
2 touches
0 conflicts
0x3c53eff1…f3d1
0x065c9d…c394
2 touches
0 conflicts
0x5f9a46e8…1402
0x065c9d…c394
2 touches
0 conflicts
0x99c170b4…b0a4
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
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:
0x00000000…001000
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity