pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,428,577
← previous block
next block →
recent activity
Analyzing
Block #74,428,577
9 transactions · 7 stateful · 2026-05-14 00:28:50 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,428,577
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
redeemDelegations
#7
0xed82b078
#8
setData
#2
0xed82b078
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fd318cd…2221
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf08dab4a…7d77
0x065c9d…c394
4 touches
1 conflict
0xfc71d092…fd49
0x065c9d…c394
3 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
2 touches
0 conflicts
0xde440bc9…5d71
0x065c9d…c394
2 touches
0 conflicts
0xdf0cfbe3…4007
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:
0x065c9d28…a9c394
1 conflict on slot
0x8fd318cd09…882221
Audit this contract →
← previous block
·
next block →
recent activity