pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,651,526
28 transactions · 22 stateful · 2026-05-10 10:01:25 UTC
Parallelism
64/100
Blocked
73%
Avg conflicts / tx
1.39
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,651,526 · 28 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
1w02w13w24w35w46w59w510w611w213w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04ad6f6f…e2a8
0xd32edf…ff58
11 touches
15 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
10 touches
10 conflicts
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xf2438038…5fa7
0x34b655…2a6f
8 touches
6 conflicts
0x0d0b2509…074d
0x3bd359…433a
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xc340aec0…e7af
0x34b655…2a6f
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
15 conflicts on slot 0x04ad6f6fc3…73e2a8
Audit this contract →
← previous block·next block →recent activity