pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,029,831
← previous block
next block →
recent activity
Analyzing
Block #73,029,831
11 transactions · 8 stateful · 2026-05-07 13:03:03 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,029,831
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0x69fc8dff
#4
0x69fc8dff
#5
0x69fc8dff
#6
0x98717539
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#3
0x121eab2f
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb389d45f…8a4c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x37b804ac…a766
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0xc8a8e6d5…0c49
0x065c9d…c394
4 touches
1 conflict
0x085bdcf2…f9fe
0x065c9d…c394
3 touches
1 conflict
0x357263ec…b0e6
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:
0x34b6552d…112a6f
1 conflict on slot
0xb389d45f2b…a98a4c
Audit this contract →
← previous block
·
next block →
recent activity