pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,334,486
← previous block
next block →
recent activity
Analyzing
Block #73,334,486
10 transactions · 7 stateful · 2026-05-08 22:50:01 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,334,486
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
updateDataFeedsValuesPartial
#5
0xed82b078
#6
0x69fe6911
#7
0xeffdedb0
#8
setData
#9
0x39435dac
#4
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x5a003a00…a0f0
0x065c9d…c394
2 touches
0 conflicts
0x8af48776…4565
0x065c9d…c394
2 touches
0 conflicts
0x989043d8…77c3
0x065c9d…c394
2 touches
0 conflicts
0xb80b785c…4d40
0x065c9d…c394
2 touches
0 conflicts
0xc08816aa…8498
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
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity