pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #70,908,460
69 transactions · 47 stateful · 2026-04-27 17:23:15 UTC
Parallelism
83/100
Blocked
70%
Avg conflicts / tx
2.09
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #70,908,460 · 69 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
1w02w13w24w35w46w57w68w79w810w911w812w913w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0xa3333039…31a8
0xd32edf…ff58
21 touches
55 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
12 touches
15 conflicts
0x1c913164…5c2e
0x34b655…2a6f
12 touches
15 conflicts
0x313f2565…5b00
0x34b655…2a6f
12 touches
15 conflicts
0x6c042c61…f883
0x34b655…2a6f
12 touches
15 conflicts
0x7b50a82b…f53d
0x34b655…2a6f
12 touches
15 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity