pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,837,494
23 transactions · 16 stateful · 2026-05-11 06:53:06 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,837,494 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w614w015w116w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c676d61…6b35
0xd32edf…ff58
13 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xeebd31ac…0794
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe429e4c9…9510
0x34b655…2a6f
6 touches
3 conflicts
0x083a8763…5a7f
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0x3c676d6160…2d6b35
Audit this contract →
← previous block·next block →recent activity