pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,283,325
← previous block
next block →
recent activity
Analyzing
Block #72,283,325
11 transactions · 9 stateful · 2026-05-04 02:09:10 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,283,325
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8003d
#2
0x9036287a
· blocks 1
#3
0x69f8003d
#4
0x69f8003d
#5
0x98717539
#6
updateDataFeedsValuesPartial
#8
setData
#9
0xeb8ce755
#10
0x39435dac
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3541f87f…17d7
0x065c9d…c394
2 touches
0 conflicts
0x793a2eea…ffad
0x065c9d…c394
2 touches
0 conflicts
0x96ab8d1f…5c21
0x065c9d…c394
2 touches
0 conflicts
0xa61a5286…ab05
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
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
0x24968e6db4…f00132
Audit this contract →
← previous block
·
next block →
recent activity