pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,338,292
← previous block
next block →
recent activity
Analyzing
Block #73,338,292
11 transactions · 9 stateful · 2026-05-08 23:15:21 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,338,292
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x9036287a
· blocks 2
#2
0x98717539
#3
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0xeffdedb0
#9
setData
#10
0x044e6100
#4
0xed82b078
· 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
0x0b390c61…dc07
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x2e1dd019…9ae5
0x065c9d…c394
2 touches
0 conflicts
0x32786b8e…319c
0x065c9d…c394
2 touches
0 conflicts
0x33113034…fe46
0x065c9d…c394
2 touches
0 conflicts
0xa0aa9ba9…df3b
0x065c9d…c394
2 touches
0 conflicts
0xa9a6bd15…8bf2
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
3 conflicts on slot
0x0b390c6160…02dc07
Audit this contract →
← previous block
·
next block →
recent activity