pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,351,528
66 transactions · 34 stateful · 2026-05-13 15:55:59 UTC
Parallelism
85/100
Blocked
71%
Avg conflicts / tx
1.24
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,351,528 · 66 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w19w110w216w023w324w426w227w340w443w550w664w465w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28805e01…188f
0xd32edf…ff58
17 touches
36 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
12 touches
15 conflicts
0x6b319071…a105
0xc8689a…ee79
8 touches
6 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
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
36 conflicts on slot 0x28805e0127…7a188f
Audit this contract →
← previous block·next block →recent activity