pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,396,836
34 transactions · 28 stateful · 2026-05-09 05:44:50 UTC
Parallelism
74/100
Blocked
46%
Avg conflicts / tx
0.97
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,396,836 · 34 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w011w112w013w214w315w016w119w020w121w222w423w525w026w527w628w729w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xc960d994…1d12
0xd32edf…ff58
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0xce8bbe33…b72e
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 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: 0x065c9d28…a9c394
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity