pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,296,460
← previous block
next block →
recent activity
Analyzing
Block #72,296,460
11 transactions · 10 stateful · 2026-05-04 03:37:22 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,296,460
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x69f814ea
#6
setData
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#10
0x39435dac
#2
0x9036287a
· blocks 1
#3
0x3f5c179b
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
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3afdfd99…b9a3
0x065c9d…c394
2 touches
0 conflicts
0x3c655a00…6f17
0x065c9d…c394
2 touches
0 conflicts
0x3dd8313a…aaa6
0x065c9d…c394
2 touches
0 conflicts
0x8e7b9a9f…1ef2
0x065c9d…c394
2 touches
0 conflicts
0xd6d6c2f7…06a6
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