pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,450,639
← previous block
next block →
recent activity
Analyzing
Block #74,450,639
9 transactions · 8 stateful · 2026-05-14 02:55:43 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,450,639
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
get_block_hash_257335279069929
#4
redeemDelegations
#5
updateDataFeedsValuesPartial
#6
0x6a053a27
#7
setData
#8
0x39435dac
#3
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e5f4899…7399
0x065c9d…c394
3 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
0x1f986b39…7102
0x065c9d…c394
2 touches
0 conflicts
0x4db1a018…a056
0x065c9d…c394
2 touches
0 conflicts
0x81fd68b0…3589
0x065c9d…c394
2 touches
0 conflicts
0x993bb044…f0b7
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
0x4e5f489972…bf7399
Audit this contract →
← previous block
·
next block →
recent activity