pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,285,730
48 transactions · 33 stateful · 2026-05-04 02:25:20 UTC
Parallelism
79/100
Blocked
73%
Avg conflicts / tx
1.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,285,730 · 48 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
2w04w05w16w27w38w19w011w012w113w415w516w118w219w621w627w730w832w133w234w335w839w941w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x24f341dc…9242
0xd32edf…ff58
11 touches
15 conflicts
0xc1ceff4b…04a0
0x3bd359…433a
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0xc13c1093…9a9d
0x754704…b603
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x46cb45de…a567
0x188d58…ea8e
8 touches
6 conflicts
0x46cb45de…a566
0x188d58…ea8e
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: 0x754704bc…afb603
21 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity