pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,331,298
44 transactions · 30 stateful · 2026-05-13 13:41:33 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
1.32
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,331,298 · 44 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
1w02w14w020w022w023w124w225w326w427w530w231w337w139w741w943w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cab84dd…a441
0x34b655…2a6f
12 touches
15 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0xc4879d37…81bf
0xd32edf…ff58
9 touches
10 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 0x7cab84dd64…b0a441
Audit this contract →
← previous block·next block →recent activity