pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,338,039
← previous block
next block →
recent activity
Analyzing
Block #73,338,039
9 transactions · 8 stateful · 2026-05-08 23:13:40 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,338,039
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x39435dac
· blocks 2
#2
0x121eab2f
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x69fe6e9b
#6
0xeffdedb0
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb389d45f…8a4c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0120051b…6384
0x065c9d…c394
2 touches
0 conflicts
0x11118c62…ce19
0x065c9d…c394
2 touches
0 conflicts
0x15b463fd…bad0
0x065c9d…c394
2 touches
0 conflicts
0x2b703da9…69cd
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:
0x34b6552d…112a6f
3 conflicts on slot
0xb389d45f2b…a98a4c
Audit this contract →
← previous block
·
next block →
recent activity