pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,460
52 transactions · 36 stateful · 2026-05-16 07:15:51 UTC
Parallelism
79/100
Blocked
72%
Avg conflicts / tx
1.52
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,920,460 · 52 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w08w210w311w012w215w323w024w125w226w327w428w529w633w134w236w337w439w440w445w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xb9868b52…c77f
0x34b655…2a6f
12 touches
15 conflicts
0x95084cde…aac7
0xd32edf…ff58
9 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0xe54a1f6f…18f2
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x3e693216…fa0e
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity