pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,426,138
← previous block
next block →
recent activity
Analyzing
Block #72,426,138
8 transactions · 4 stateful · 2026-05-04 18:01:25 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,426,138
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xeea270…6b21
#3
execute
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d013b8f…7484
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x92989da3…e23b
0x065c9d…c394
3 touches
1 conflict
0x9db30209…6c09
0x065c9d…c394
3 touches
1 conflict
0x15ba78ed…64c0
0x065c9d…c394
3 touches
1 conflict
0x6218280d…629c
0x065c9d…c394
2 touches
0 conflicts
0x90a6030d…08e3
0x065c9d…c394
2 touches
0 conflicts
0xcf41bef6…b6fd
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
0x6d013b8f24…d77484
Audit this contract →
← previous block
·
next block →
recent activity