pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,859,029
← previous block
next block →
recent activity
Analyzing
Block #72,859,029
11 transactions · 9 stateful · 2026-05-06 18:06:15 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,859,029
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x20dd17…72bb
#2
execute
#3
0x121eab2f
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePriceFeedsIfNecessary
#9
forwardEth
#10
0xeffdedb0
#4
0x121eab2f
· blocks 1
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…000b
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbb
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbc
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbd
0x6ca43f…c331
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
4 touches
1 conflict
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity