pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,956,652
34 transactions · 25 stateful · 2026-04-27 22:44:05 UTC
Parallelism
71/100
Blocked
64%
Avg conflicts / tx
1.76
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #70,956,652 · 34 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
8w09w110w211w312w013w114w215w316w417w518w628w529w630w731w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8a0d91a0…2b15
0x34b655…2a6f
14 touches
21 conflicts
0x47b2d2eb…8aa5
0x34b655…2a6f
12 touches
15 conflicts
0x00f245ce…1e10
0x34b655…2a6f
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
10 touches
10 conflicts
0x50c2960c…5f37
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity