pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,344,879
42 transactions · 28 stateful · 2026-05-13 15:11:49 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
0.95
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,344,879 · 42 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w28w09w111w312w013w114w223w024w025w127w230w431w532w633w736w839w240w341w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6362e7fa…6795
0xd32edf…ff58
11 touches
15 conflicts
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
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: 0xd32edf66…9fff58
15 conflicts on slot 0x6362e7fa0c…186795
Audit this contract →
← previous block·next block →recent activity