pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,070,083
32 transactions · 27 stateful · 2026-04-28 11:19:26 UTC
Parallelism
66/100
Blocked
52%
Avg conflicts / tx
1.06
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #71,070,083 · 32 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w19w010w111w212w314w015w116w017w018w119w123w424w525w626w727w828w929w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0x3254d19b…f714
0x34b655…2a6f
6 touches
3 conflicts
0x3c35979a…975d
0x34b655…2a6f
6 touches
3 conflicts
0x3e1f7818…2fc8
0x34b655…2a6f
6 touches
3 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
6 touches
3 conflicts
0x62d6e82b…a750
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity