pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,089,913
30 transactions · 29 stateful · 2026-04-28 13:31:36 UTC
Parallelism
63/100
Blocked
66%
Avg conflicts / tx
1.73
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #71,089,913 · 30 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w06w17w08w09w110w211w312w414w116w117w120w421w523w725w926w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x59ef13ba…2741
0x34b655…2a6f
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0xa21e8abe…a7f1
0x34b655…2a6f
8 touches
6 conflicts
0x75f6889e…7f1e
0x34b655…2a6f
6 touches
3 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity