pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,649,396
← previous block
next block →
recent activity
Analyzing
Block #73,649,396
8 transactions · 6 stateful · 2026-05-10 09:47:08 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,649,396
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
updateDataFeedsValuesPartial
#3
0x6c05cd2b
#4
0x9036287a
· blocks 2
#7
setData
#5
0x0c7abd22
· blocks 1
#6
0x62be7533
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc800ae2a…cd91
0x065c9d…c394
5 touches
3 conflicts
0xc9e97522…3519
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
2 touches
0 conflicts
0xd64df631…404c
0x000000…012a
2 touches
0 conflicts
0x24fe818f…bb82
0x2cb31c…7777
2 touches
0 conflicts
0x4f3c51de…3f91
0x2cb31c…7777
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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:
0x065c9d28…a9c394
3 conflicts on slot
0xc800ae2af8…edcd91
Audit this contract →
← previous block
·
next block →
recent activity