pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,525,784
69 transactions · 34 stateful · 2026-05-19 02:49:05 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
1.78
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #75,525,784 · 69 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w27w310w313w324w332w433w335w443w547w857w1063w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd07b981…5250
0xd32edf…ff58
25 touches
78 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
10 touches
10 conflicts
0x00f7e3b7…e017
0x188d58…ea8e
10 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
10 touches
10 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x892daf6e…48d8
0x065c9d…c394
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
78 conflicts on slot 0xbd07b98128…1d5250
Audit this contract →
← previous block·next block →recent activity