pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,342,847
53 transactions · 33 stateful · 2026-05-13 14:58:20 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
2.38
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #74,342,847 · 53 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w19w111w213w022w323w124w226w127w228w329w430w531w632w734w837w938w1039w1141w1244w1345w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02b91642…1d79
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0xb00ff82e…2ec2
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
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
105 conflicts on slot 0x02b91642ec…ca1d79
Audit this contract →
← previous block·next block →recent activity