pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,271,569
← previous block
next block →
recent activity
Analyzing
Block #72,271,569
11 transactions · 10 stateful · 2026-05-04 00:50:09 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,271,569
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9036287a
· blocks 2
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
forward
#7
0xed82b078
· blocks 1
#9
0x69f7edb9
#10
setData
#5
0x3f5c179b
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
7
w0
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x62f52ece…d37d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc80843b0…6750
0x065c9d…c394
3 touches
1 conflict
0xe5fab735…e80d
0x065c9d…c394
3 touches
1 conflict
0xd550b071…6803
0x065c9d…c394
2 touches
0 conflicts
0xda8ee426…738c
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
3 conflicts on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity