pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,239,214
29 transactions · 25 stateful · 2026-04-29 06:05:25 UTC
Parallelism
62/100
Blocked
72%
Avg conflicts / tx
2.34
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #71,239,214 · 29 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
1w02w15w16w07w18w29w310w411w012w113w214w315w416w517w618w719w825w328w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xb1dcb4b3…4b74
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xb857c1…9be1
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
10 touches
10 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 conflicts
0x7007d963…9003
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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity