pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,092,391
50 transactions · 40 stateful · 2026-04-28 13:48:07 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #71,092,391 · 50 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w010w012w122w023w124w225w328w029w130w231w135w236w237w138w240w345w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x23114fac…630a
0x34b655…2a6f
6 touches
3 conflicts
0x3c35979a…975d
0x34b655…2a6f
6 touches
3 conflicts
0x3e1f7818…2fc8
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: 0x34b6552d…112a6f
6 conflicts on slot 0x8c49c85c3e…afee96
Audit this contract →
← previous block·next block →recent activity