pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,289
← previous block
next block →
recent activity
Analyzing
Block #72,283,289
13 transactions · 11 stateful · 2026-05-04 02:08:55 UTC
Parallelism
85
/100
Blocked
18
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,289
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0x69f8002f
· blocks 1
#3
0x9036287a
· blocks 1
#4
0x98717539
#6
0x69f8002f
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0x0c7abd22
#11
forward
#12
setData
#5
0x69f8002f
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
5
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d49c95a…9780
0x065c9d…c394
2 touches
0 conflicts
0xdbb56ff0…abf5
0x065c9d…c394
2 touches
0 conflicts
0xe3cc63ba…966d
0x065c9d…c394
2 touches
0 conflicts
0xeb09c7bb…4be3
0x065c9d…c394
2 touches
0 conflicts
0xf92bbfdf…4dac
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity