pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,589,938
← previous block
next block →
recent activity
Analyzing
Block #74,589,938
12 transactions · 11 stateful · 2026-05-14 18:29:30 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,589,938
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updatePrices
#3
multicall
#4
setData
#5
redeemDelegations
· blocks 1
#6
redeemDelegations
#8
forward
#9
0x5339c59f
#10
0x5339c59f
#11
0x6a061501
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x68f33f…42bc
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0002
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0004
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…000c
0x023eb9…b2b4
2 touches
0 conflicts
0x5278f938…51a2
0x188d58…ea8e
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:
0x68f33f95…3942bc
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity