pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,090,125
57 transactions · 41 stateful · 2026-04-28 13:33:01 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.37
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,090,125 · 57 txs across 13 waves · depth 13
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
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w19w010w113w216w018w125w226w027w128w229w330w433w534w635w738w350w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xf853eb8e…4027
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x801a6e57…d85c
0x34b655…2a6f
10 touches
10 conflicts
0x9d651568…2c87
0x34b655…2a6f
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0xb378025c…30cf
0x34b655…2a6f
8 touches
6 conflicts
0xc3aacf13…6b3d
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity