pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,010,137
← previous block
next block →
recent activity
Analyzing
Block #74,010,137
7 transactions · 6 stateful · 2026-05-12 02:05:37 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,010,137
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
redeemDelegations
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9dc2c93…da85
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x28be172f…6676
0x065c9d…c394
2 touches
0 conflicts
0x3a5695b3…e1e4
0x065c9d…c394
2 touches
0 conflicts
0x626b5698…1b38
0x065c9d…c394
2 touches
0 conflicts
0x9c4bda7c…533d
0x065c9d…c394
2 touches
0 conflicts
0xba012313…3aca
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:
0xd32edf66…9fff58
1 conflict on slot
0xe9dc2c931c…ddda85
Audit this contract →
← previous block
·
next block →
recent activity