pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,630,395
43 transactions · 30 stateful · 2026-05-14 23:00:01 UTC
Parallelism
77/100
Blocked
73%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,630,395 · 43 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
1w02w03w14w06w09w111w112w113w214w315w020w122w023w124w226w227w328w429w531w232w338w541w842w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe052c198…cfc0
0xd32edf…ff58
11 touches
15 conflicts
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
6 touches
3 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity