pev.One block, wave by wave
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,892,143
45 transactions · 35 stateful · 2026-04-27 15:34:34 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
2.16
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #70,892,143 · 45 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w18w210w011w112w214w315w416w517w618w719w821w922w1023w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
24 touches
66 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x94e7f277…471b
0x34b655…2a6f
10 touches
10 conflicts
0x374426df…f445
0xc8689a…ee79
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1b0
0x8d66a4…3095
8 touches
6 conflicts
0x468c69b1…af11
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
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: 0xb857c13a…1a9be1
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity