pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,202,088
← previous block
next block →
recent activity
Analyzing
Block #73,202,088
13 transactions · 9 stateful · 2026-05-08 08:09:16 UTC
Parallelism
85
/100
Blocked
22
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,202,088
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
· blocks 2
#2
0x5bf9264c
#3
0x5bf9264c
#4
updateDataFeedsValuesPartial
#7
forward
#8
forward
#9
0xed82b078
#10
0xed82b078
#11
0xeffdedb0
#12
setData
#5
0x62be7533
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6415c661…a905
0x065c9d…c394
3 touches
1 conflict
0x00000000…0000
0x100fb1…875e
2 touches
0 conflicts
0x00000000…0002
0x100fb1…875e
2 touches
0 conflicts
0xe09eda07…8dda
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
0x7f189cf621…beafab
Audit this contract →
← previous block
·
next block →
recent activity