pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,977,599
← previous block
next block →
recent activity
Analyzing
Block #72,977,599
9 transactions · 9 stateful · 2026-05-07 07:15:27 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,977,599
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
updateDataFeedsValuesPartial
#3
forward
#6
0xeffdedb0
#7
setData
#8
0x39435dac
#4
0x5339c59f
· blocks 1
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x102370ff…22bc
0x065c9d…c394
4 touches
1 conflict
0x8554d42c…1f28
0x065c9d…c394
2 touches
0 conflicts
0xaeae6f96…a4fe
0x065c9d…c394
2 touches
0 conflicts
0xe4da7ec3…f318
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
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
0xbd7e37a9b5…859eb5
Audit this contract →
← previous block
·
next block →
recent activity