pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,410,599
← previous block
next block →
recent activity
Analyzing
Block #74,410,599
10 transactions · 9 stateful · 2026-05-13 22:29:17 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,410,599
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updateDataFeedsValuesPartial
#3
addLiquidity
· blocks 1
#4
redeemDelegations
#6
setData
#7
forward
#8
0x64480813
#9
0x6a04fbb5
#5
claim
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x8b0d32…7367
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1543e463…37b4
0x065c9d…c394
2 touches
0 conflicts
0x5a0a316d…ba8d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x7f045645…cf5f
0x065c9d…c394
2 touches
0 conflicts
0x8ea73483…de24
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:
0x8b0d325f…457367
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity