pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,911,349
36 transactions · 28 stateful · 2026-04-27 17:42:29 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #70,911,349 · 36 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w18w215w016w117w218w219w324w025w126w128w229w230w331w432w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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: 0x065c9d28…a9c394
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity