pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,651,605
← previous block
next block →
recent activity
Analyzing
Block #73,651,605
10 transactions · 9 stateful · 2026-05-10 10:01:57 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,651,605
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updatePrices
#5
0x98717539
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
0x6a00580d
#9
setData
#2
0x0c7abd22
· blocks 1
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb5ad669…9f39
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x083c173a…f927
0x065c9d…c394
2 touches
0 conflicts
0x645c9dec…b2fb
0x065c9d…c394
2 touches
0 conflicts
0x6902e7b5…c916
0x065c9d…c394
2 touches
0 conflicts
0x695ed80e…dd1f
0x065c9d…c394
2 touches
0 conflicts
0x6be5d481…cc28
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:
0xd32edf66…9fff58
3 conflicts on slot
0xcb5ad669a5…969f39
Audit this contract →
← previous block
·
next block →
recent activity