pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,335,690
47 transactions · 39 stateful · 2026-05-13 14:10:41 UTC
Parallelism
70/100
Blocked
74%
Avg conflicts / tx
2.36
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,335,690 · 47 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w18w29w010w211w012w115w016w117w218w319w420w521w636w137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x886f7fe6…8b7a
0x34b655…2a6f
10 touches
10 conflicts
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xafd59af5…5257
0xc8689a…ee79
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x7cb2f3fa…4836
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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity