pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,396,657
39 transactions · 31 stateful · 2026-05-09 05:43:38 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.74
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,396,657 · 39 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w18w210w011w014w315w016w117w218w319w120w224w325w426w527w630w732w833w937w838w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5defe5a…c846
0xd32edf…ff58
19 touches
45 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa7fe0d97…ae1c
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0xb8c315fa…b168
0x065c9d…c394
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 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
45 conflicts on slot 0xa5defe5a44…39c846
Audit this contract →
← previous block·next block →recent activity