pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,974,609
← previous block
next block →
recent activity
Analyzing
Block #72,974,609
10 transactions · 9 stateful · 2026-05-07 06:55:29 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
#72,974,609
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6943a490
#3
setData
#4
forward
#5
0xed82b078
· blocks 2
#8
0x69fc37d9
#9
0xeffdedb0
#6
0xed82b078
· blocks 1
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0x2bf3acbe…5610
0x2185cd…21c7
2 touches
0 conflicts
0xa1d075fe…dbda
0x2ae0cf…3d4e
2 touches
0 conflicts
0xa1d075fe…dbdf
0x2ae0cf…3d4e
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
0xce7bfe5ef1…205e58
Audit this contract →
← previous block
·
next block →
recent activity