pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,421,698
40 transactions · 34 stateful · 2026-04-30 02:21:23 UTC
Parallelism
77/100
Blocked
74%
Avg conflicts / tx
1.98
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #71,421,698 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w18w012w014w115w116w017w118w219w321w122w223w324w425w526w627w228w736w439w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6c0f1ca…9b6b
0xd32edf…ff58
17 touches
36 conflicts
0x15698ac9…2a46
0x34b655…2a6f
12 touches
15 conflicts
0x085df2c1…305a
0x34b655…2a6f
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 conflicts
0x21d22421…0b7a
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
0x34b655…2a6f
8 touches
6 conflicts
0x3b74ae43…a235
0x34b655…2a6f
8 touches
6 conflicts
0x3c35979a…975d
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: 0xd32edf66…9fff58
36 conflicts on slot 0xc6c0f1ca4e…109b6b
Audit this contract →
← previous block·next block →recent activity