pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,090,055
56 transactions · 39 stateful · 2026-04-28 13:32:33 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.13
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #71,090,055 · 56 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
1w02w15w17w011w212w223w124w025w126w227w331w032w146w451w753w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc21fc18f…f530
0xd32edf…ff58
9 touches
10 conflicts
0x21d22421…0b7a
0x34b655…2a6f
8 touches
6 conflicts
0x3b74ae43…a235
0x34b655…2a6f
8 touches
6 conflicts
0x3c35979a…975d
0x34b655…2a6f
8 touches
6 conflicts
0x3e1f7818…2fc8
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity