pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,035,653
26 transactions · 22 stateful · 2026-05-07 13:41:49 UTC
Parallelism
50/100
Blocked
59%
Avg conflicts / tx
2.46
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,035,653 · 26 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w311w412w513w614w715w816w923w1025w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
20 touches
45 conflicts
0x388e001a…7e04
0x34b655…2a6f
18 touches
36 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
18 touches
36 conflicts
0xe7574014…95e2
0x34b655…2a6f
18 touches
36 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xc6417de0…2191
0xc8689a…ee79
18 touches
36 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
16 touches
28 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
16 touches
28 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
45 conflicts on slot 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity