pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,762,013
42 transactions · 32 stateful · 2026-05-15 13:38:33 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,762,013 · 42 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w110w011w012w114w015w116w217w318w419w521w125w536w638w839w940w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x7d6df307…45ba
0xd32edf…ff58
11 touches
15 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0x9be2b99a…a959
0x34b655…2a6f
8 touches
6 conflicts
0x9cc607d0…c9c7
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity