pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,911,035
36 transactions · 32 stateful · 2026-04-27 17:40:24 UTC
Parallelism
72/100
Blocked
66%
Avg conflicts / tx
1.67
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #70,911,035 · 36 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
1w02w13w26w07w18w29w310w011w012w113w214w215w316w318w121w222w323w429w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xe6455d1f…1029
0x754704…b603
10 touches
10 conflicts
0x757254ae…d917
0x34b655…2a6f
10 touches
10 conflicts
0x0d0b2509…074d
0x3bd359…433a
10 touches
10 conflicts
0x00000000…0002
0xb857c1…9be1
8 touches
6 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
8 touches
6 conflicts
0x12e7c471…901c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity