pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,439,939
← previous block
next block →
recent activity
Analyzing
Block #74,439,939
10 transactions · 8 stateful · 2026-05-14 01:44:32 UTC
Parallelism
60
/100
Blocked
50
%
Avg conflicts / tx
0.7
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,439,939
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x1ffa3c9b
· blocks 4
#2
updatePrices
#3
updatePrices
#4
updateDataFeedsValuesPartial
#9
setData
#5
0x5339c59f
· blocks 1
#6
0x5339c59f
· blocks 1
#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
5
w1
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd707d645…e6b6
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xa7f89e3d…b7ff
0x065c9d…c394
3 touches
1 conflict
0x653bea22…f542
0x065c9d…c394
3 touches
1 conflict
0xc1e77ee9…5621
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity