pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,429,467
12 transactions · 9 stateful · 2026-05-04 18:23:32 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,429,467 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x24216e94…9055
0x065c9d…c394
2 touches
0 conflicts
0x365d953f…8e00
0x065c9d…c394
2 touches
0 conflicts
0x7e438c85…f897
0x065c9d…c394
2 touches
0 conflicts
0x8f928f69…2f2a
0x065c9d…c394
2 touches
0 conflicts
0xe0e33513…1cab
0x065c9d…c394
2 touches
0 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: 0x065c9d28…a9c394
3 conflicts on slot 0xffe431af56…838faa
Audit this contract →
← previous block·next block →recent activity