pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,301,118
← previous block
next block →
recent activity
Analyzing
Block #72,301,118
8 transactions · 8 stateful · 2026-05-04 04:08:25 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,301,118
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0d484c28
· blocks 1
#2
0x9036287a
· blocks 1
#3
updateDataFeedsValuesPartial
#6
0x69f81c31
#7
setData
#4
0x3f5c179b
#5
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4c5de40f…e7f5
0x065c9d…c394
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x4066dc16…df81
0x065c9d…c394
3 touches
1 conflict
0xbad89b7f…8fda
0x065c9d…c394
3 touches
1 conflict
0xe3024c4c…d234
0xa6afd3…d132
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity