pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,394,623
45 transactions · 43 stateful · 2026-05-04 14:31:22 UTC
Parallelism
78/100
Blocked
67%
Avg conflicts / tx
2.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,394,623 · 45 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
1w02w03w04w16w18w09w110w211w312w413w514w615w716w817w930w132w234w335w336w437w538w639w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
20 touches
45 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xadac4a86…c2bc
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0xffe431af…8faa
0x065c9d…c394
8 touches
6 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x0c05ae63…f1f2
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: 0x7e9d3a8a…4f9fda
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity