pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,458,709
← previous block
next block →
recent activity
Analyzing
Block #72,458,709
8 transactions · 7 stateful · 2026-05-04 21:38:25 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,458,709
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0x3f5c179b
· blocks 1
#4
forward
#5
updateDataFeedsValuesPartial
#6
setApprovalForAll
#7
setData
#3
multicall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b9162a5…8cc5
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
0x30d737f7…0ffb
0x065c9d…c394
2 touches
0 conflicts
0x62d3c911…5abd
0x065c9d…c394
2 touches
0 conflicts
0xdaf14825…aa3b
0x065c9d…c394
2 touches
0 conflicts
0xf1c6599c…6596
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x9b9162a574…9c8cc5
Audit this contract →
← previous block
·
next block →
recent activity