pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,996,212
32 transactions · 24 stateful · 2026-04-28 03:07:41 UTC
Parallelism
84/100
Blocked
58%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #70,996,212 · 32 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w010w111w212w313w416w017w118w019w120w221w322w023w125w027w128w129w231w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xdbc578df…706a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x30a225d6…6679
0x34b655…2a6f
4 touches
1 conflict
0x629de12a…8773
0x34b655…2a6f
4 touches
1 conflict
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
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: 0xb857c13a…1a9be1
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity