pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,415,505
← previous block
next block →
recent activity
Analyzing
Block #74,415,505
10 transactions · 10 stateful · 2026-05-13 23:01:51 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,415,505
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updatePrices
#3
0x98717539
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
· blocks 1
#8
setData
#9
0x39435dac
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x80f0f9…5f5f
4 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
0xb05f613c…b694
0x065c9d…c394
2 touches
0 conflicts
0xe00eb6fd…c0c0
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x0872abbe…9c39
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:
0x80f0f92a…315f5f
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity