pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,233,613
76 transactions · 50 stateful · 2026-05-03 20:35:03 UTC
Parallelism
79/100
Blocked
72%
Avg conflicts / tx
2.24
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #72,233,613 · 76 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w59w512w613w723w825w931w533w1064w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
30 touches
105 conflicts
0xaf498679…7732
0x34b655…2a6f
20 touches
45 conflicts
0x35b85d8e…1edd
0x34b655…2a6f
20 touches
45 conflicts
0x00f245ce…1e10
0x34b655…2a6f
20 touches
45 conflicts
0x50c2960c…5f37
0x34b655…2a6f
20 touches
45 conflicts
0xac2a0273…721b
0x34b655…2a6f
20 touches
45 conflicts
0xcd5c7f64…ad4b
0x34b655…2a6f
20 touches
45 conflicts
0xafd59af5…5257
0xc8689a…ee79
20 touches
45 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
105 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity