pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,429,013
← previous block
next block →
recent activity
Analyzing
Block #72,429,013
9 transactions · 7 stateful · 2026-05-04 18:20:30 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,429,013
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
0x72d213…8180
#2
0xed82b078
· blocks 1
#3
updateDataFeedsValuesPartial
#6
forward
#7
0x69f8e3e6
#8
setData
#4
undelegate
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0001
0x000000…1000
2 touches
0 conflicts
0x0b000000…0006
0x000000…1000
2 touches
0 conflicts
0x0b000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0007
0x000000…1000
2 touches
0 conflicts
0x0c7142f7…ef91
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity