pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,972
64 transactions · 34 stateful · 2026-05-18 21:28:09 UTC
Parallelism
73/100
Blocked
74%
Avg conflicts / tx
2.38
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,478,972 · 64 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w16w17w113w217w318w420w525w526w232w637w758w859w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1eb5426a…c8f0
0xd32edf…ff58
27 touches
91 conflicts
0x17606ba6…1b6e
0x754704…b603
16 touches
28 conflicts
0x846f2172…fd54
0x0555e3…2b9c
14 touches
21 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
10 touches
10 conflicts
0xe75ce681…ba60
0x188d58…ea8e
10 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
8 touches
6 conflicts
0x09beabbc…065c
0x188d58…ea8e
8 touches
6 conflicts
0x09beabbc…065e
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 0x1eb5426a85…9ac8f0
Audit this contract →
← previous block·next block →recent activity