pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,995,890
53 transactions · 41 stateful · 2026-04-28 03:05:34 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.66
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #70,995,890 · 53 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w28w09w314w126w027w128w229w330w431w538w639w740w841w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0x374426df…f445
0xc8689a…ee79
12 touches
15 conflicts
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xdf889704…8950
0x34b655…2a6f
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 conflicts
0x87a380d9…2d04
0x34b655…2a6f
8 touches
6 conflicts
0x893cd52c…5766
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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity