pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,594
59 transactions · 41 stateful · 2026-05-10 10:01:53 UTC
Parallelism
75/100
Blocked
71%
Avg conflicts / tx
2.41
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,651,594 · 59 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w919w224w329w445w1046w1147w1248w1349w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47c00637…a4fd
0xd32edf…ff58
29 touches
105 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
12 touches
15 conflicts
0x00000000…0000
0x63e48b…53f2
12 touches
15 conflicts
0x9a555477…19a8
0x754704…b603
12 touches
15 conflicts
0x00000000…0004
0x63e48b…53f2
12 touches
15 conflicts
0x00000000…0002
0x63e48b…53f2
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: 0xd32edf66…9fff58
105 conflicts on slot 0x47c0063751…8ca4fd
Audit this contract →
← previous block·next block →recent activity