pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,029,783
41 transactions · 32 stateful · 2026-05-07 13:02:44 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.78
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,029,783 · 41 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w325w429w730w131w832w233w834w935w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
16 touches
28 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xb389d45f…8a4c
0x34b655…2a6f
12 touches
15 conflicts
0x70b2f813…783c
0x2a68ba…90c5
12 touches
15 conflicts
0x7e959c4d…1c27
0xd32edf…ff58
11 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity