pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,349,174
57 transactions · 38 stateful · 2026-05-09 00:27:46 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
3.4
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #73,349,174 · 57 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w17w18w214w315w017w420w121w222w523w624w126w731w332w433w534w635w736w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb93d580…a95e
0xd32edf…ff58
37 touches
171 conflicts
0x12309510…0ac2
0x000000…012a
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0x4dd1db39…a994
0x188d58…ea8e
8 touches
6 conflicts
0x4dd1db39…a996
0x188d58…ea8e
8 touches
6 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
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: 0xd32edf66…9fff58
171 conflicts on slot 0xbb93d5808c…97a95e
Audit this contract →
← previous block·next block →recent activity