pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,662
59 transactions · 34 stateful · 2026-05-18 21:26:02 UTC
Parallelism
70/100
Blocked
71%
Avg conflicts / tx
2.85
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #75,478,662 · 59 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w16w211w314w418w222w525w630w732w837w952w1055w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84af2e08…f387
0xd32edf…ff58
27 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
24 touches
66 conflicts
0x0dbf9688…c6cf
0xd18b7e…414b
12 touches
15 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
12 touches
15 conflicts
0xe75ce681…ba60
0x188d58…ea8e
12 touches
15 conflicts
0x56a919c4…ab49
0xee8c0e…1242
10 touches
10 conflicts
0x729c91b8…9537
0x188d58…ea8e
10 touches
10 conflicts
0x729c91b8…9538
0x188d58…ea8e
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: 0xd32edf66…9fff58
91 conflicts on slot 0x84af2e08dd…66f387
Audit this contract →
← previous block·next block →recent activity