pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,492,004
← previous block
next block →
recent activity
Analyzing
Block #74,492,004
10 transactions · 7 stateful · 2026-05-14 07:31:02 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,492,004
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
deposit
· blocks 1
#3
updateDataFeedsValuesPartial
#4
setMerkleRoot
#5
setData
#7
deposit
#8
0xdf08d9…5d3f
#9
0x40d050…1837
#6
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x6946d7b5…3c0d
0x065c9d…c394
2 touches
0 conflicts
0x84a9f762…1d7f
0x065c9d…c394
2 touches
0 conflicts
0x95cca082…4b78
0x065c9d…c394
2 touches
0 conflicts
0xae1f0667…e670
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:
USDC (USDC)
1 conflict on slot
0xa1087a5ca6…0a66c4
Audit this contract →
← previous block
·
next block →
recent activity