pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,079,481
51 transactions · 46 stateful · 2026-05-17 00:58:45 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
2.88
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #75,079,481 · 51 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w27w08w39w110w411w513w117w018w119w228w330w332w538w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x7a2066a9…9d2e
0xd32edf…ff58
13 touches
21 conflicts
0x631b4113…baa9
0x34b655…2a6f
12 touches
15 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xb7ce83b1…2c96
0x34b655…2a6f
10 touches
10 conflicts
0x014b941d…ccce
0x34b655…2a6f
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: 0x34b6552d…112a6f
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity