pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,984,245
← previous block
next block →
recent activity
Analyzing
Block #72,984,245
11 transactions · 9 stateful · 2026-05-07 07:59:55 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,984,245
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0xcf7468f4
#5
0x98717539
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x69fc46f3
#9
0xeffdedb0
#10
0x39435dac
#2
0x0c7abd22
· blocks 1
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x6fe22e12…1f3a
0x065c9d…c394
4 touches
1 conflict
0x4423491e…8e1e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x021440fa…9bf5
0xd32edf…ff58
3 touches
1 conflict
0x1e45a77f…0257
0x065c9d…c394
3 touches
1 conflict
0x52446f1e…0908
0x065c9d…c394
3 touches
1 conflict
0xaa4acedb…86de
0x065c9d…c394
3 touches
1 conflict
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
0x0b390c6160…02dc07
Audit this contract →
← previous block
·
next block →
recent activity