pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,468
49 transactions · 32 stateful · 2026-05-10 10:01:02 UTC
Parallelism
75/100
Blocked
69%
Avg conflicts / tx
1.86
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #73,651,468 · 49 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
1w04w16w012w114w216w219w321w422w023w124w225w327w430w531w632w733w534w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d83346a…a926
0xd32edf…ff58
23 touches
66 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0x0d0b2509…074d
0x3bd359…433a
8 touches
6 conflicts
0xc9e97522…3519
0x2a68ba…90c5
6 touches
3 conflicts
0xc34a0420…db6a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf2438038…5fa7
0x34b655…2a6f
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
66 conflicts on slot 0x7d83346aef…f4a926
Audit this contract →
← previous block·next block →recent activity