pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,496,830
← previous block
next block →
recent activity
Analyzing
Block #72,496,830
11 transactions · 8 stateful · 2026-05-05 01:52:09 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,496,830
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute_route
#3
0xa96df62f
#4
0x69f94dc1
#5
updatePrices
#7
updateDataFeedsValuesPartial
#8
0x69f94dc1
#9
transfer
#10
setData
#6
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb88da7cd…07af
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xed0c29b5…e315
0x065c9d…c394
4 touches
1 conflict
0xa37148b8…5380
0x065c9d…c394
3 touches
1 conflict
0xee588687…55b0
0x065c9d…c394
3 touches
1 conflict
0x50c8ea77…d643
0x065c9d…c394
3 touches
1 conflict
0x3e08b466…5224
0x065c9d…c394
3 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:
0x065c9d28…a9c394
1 conflict on slot
0xb88da7cd4a…2007af
Audit this contract →
← previous block
·
next block →
recent activity